Run a pre-mortem before committing to a plan
Imagine the plan has already failed and ask what went wrong.
Why it works
A pre-mortem temporarily assumes failure and asks people to explain it, which licenses voicing concerns that confirmation bias and social pressure would otherwise suppress. By framing failure as the already-happened reality, it shifts the question from "might this fail?" (easy to dismiss) to "how did this fail?" (harder to dismiss, produces more concrete failure modes). Gary Klein’s research showed this increased identification of potential problems compared to standard prospective evaluation.
How to do it
- After finalizing a plan but before committing resources, say: "It is twelve months from now, and this plan has failed. What happened?"
- Have everyone generate failure causes independently before discussing — prevents groupthink.
- Collect the list and address each failure mode explicitly, either with a mitigation or with a revised expectation.
- Do not skip the step because the plan "looks solid" — that confidence is exactly when the pre-mortem is most needed.
Evidence
Klein (2007) found that pre-mortems increased identification of potential problems by about 30% compared to standard prospective evaluation in a controlled study. The technique is now widely used in project management and has replications across organizational settings. (observational)
The 30% estimate is from one study with specific conditions; effect sizes vary by group composition, stakes, and how seriously the exercise is taken.
Sources
- Klein (2007), performing a project premortem, Harvard Business Review
- Klein, G. (2007). Performing a project premortem. Harvard Business Review, 85(9), 18–19.
Common mistake
Treating the pre-mortem as a formality — listing superficial failure modes to check the box, then dismissing them because the team is confident.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Confirmation Bias: Seeing What You Expect to See
- Deliberately consider the opposite hypothesis
For any belief you are testing, explicitly generate the strongest case for the opposing view.
- Deliberately seek out sources that disagree with you
For any important belief, find and read the best-regarded opposing view.
- Invite an adversarial collaborator
Find someone whose genuine prior is the opposite of yours, and work together on the same evidence.
- Maintain a belief-tracking log with timestamps
Record your beliefs and confidence levels before evidence arrives, so you can see whether you actually updated.
- Red-team your plan with a formal adversarial review
Assign someone the explicit role of finding every way your plan could be wrong or fail.
- Structure the analysis before searching for evidence
Define what you’re looking for and what would count as evidence before starting your search.
Related concepts
- Bayesian Thinking: How to Update Beliefs Rationally
Holding beliefs as probabilities and updating them when evidence arrives
- Thinking, Fast and Slow, Made Usable
Two systems, the biases they create, and when to slow down
- Mental Models: Charlie Munger’s Latticework Approach
Building the multi-disciplinary toolkit that lets you see what single-discipline thinkers miss
- The Availability Heuristic: Why Memorable Feels Probable
The mental shortcut that makes vivid and recent feel probable — and the practices that correct for it