The Pre-Mortem Technique: How to Kill Bad Ideas Before They Cost You
Most teams do post-mortems — examining what went wrong after a project has already failed. The pre-mortem technique flips this logic entirely. Instead of waiting for failure to arrive, you simulate it in advance. Before a project launches, before money is spent, before reputations are on the line, you ask: “Assume this has failed catastrophically. What killed it?” It sounds morbid. It works precisely because of that.
What the Pre-Mortem Technique Actually Is
The pre-mortem was formalized by psychologist Gary Klein in the late 1990s and popularized through his research on decision-making under pressure. The mechanics are straightforward. Before committing to a plan, you gather the people involved and instruct them to imagine it is one year in the future. The project has failed — not stumbled, but failed completely. Each person then writes down, independently, every reason they can think of that caused that failure.
The independent writing step matters. When people generate ideas separately before sharing them, you get a wider range of reasons. Group discussion alone tends to narrow thinking quickly as people anchor to the first ideas spoken aloud — a phenomenon known as anchoring bias.
After individual generation, reasons are shared and grouped. The team then examines which risks are most credible and which can be addressed before launch. The result is not a list of complaints. It is a structured threat assessment produced before the threat materializes.
Why We Need a Technique Like This in the First Place
The uncomfortable truth is that humans are poorly wired for honest evaluation of their own plans. Two cognitive biases are especially destructive here.
Optimism bias is the tendency to overestimate the likelihood of positive outcomes and underestimate the probability of negative ones. Studies consistently show that people rate their own projects as more likely to succeed than statistically similar projects run by others. This is not arrogance — it is a systematic feature of human cognition.
The second bias is more socially driven. Groupthink is the tendency for cohesive groups to suppress dissenting opinions in favor of consensus and harmony. Once a plan has momentum — once a team is enthusiastic, a manager is invested, or a deadline is approaching — raising doubts becomes socially costly. People stay quiet not because they have no concerns, but because voicing concerns feels like betrayal or pessimism.
The pre-mortem works around both problems. By framing criticism as a hypothetical exercise rather than a personal attack on the plan, it gives people permission to say what they actually think. The question is not “what do you think could go wrong?” — which invites people to hedge. The question is “it has already gone wrong — why?” This subtle shift in framing unlocks a different kind of thinking.
A Real-World Example: NASA and the Space Shuttle Challenger
The 1986 Challenger disaster is one of the most studied examples of organizational decision failure in history. Engineers at Morton Thiokol had serious reservations about launching in cold temperatures, specifically about the reliability of the O-ring seals. Those concerns were raised. They were also overridden.
What made the difference was not a lack of information — the information existed. What was missing was a structured process that gave dissenting voices equal standing. The social pressure to launch was immense. A formal pre-mortem, conducted before that decision, would not have guaranteed a different outcome, but it would have forced the question directly: “Assume the shuttle is destroyed on launch. Why did that happen?” An engineer answering that question in writing, before any discussion, would almost certainly have written “O-ring failure in cold temperatures.” That answer would have been on the table, in black and white, demanding a response.
The lesson is not that pre-mortems are magic. It is that organizational culture routinely silences the people who already know what the problems are.
How to Run a Pre-Mortem Effectively
The technique is simple but easy to botch. Here is what separates a useful pre-mortem from a performative one.
- Run it before commitment, not after. A pre-mortem conducted once a plan is already approved is largely theater. People feel psychologically committed to what has been decided, a phenomenon called the sunk cost fallacy. The technique must be used while the plan is still genuinely open to revision.
- Make written generation mandatory. Every participant writes independently before anyone speaks. This prevents dominant voices from setting the agenda and captures concerns that people might otherwise self-censor.
- Include people outside the core team. People closest to a project are most susceptible to optimism bias. Someone one step removed — from a different department, or with experience in a similar domain — often spots structural risks that insiders have normalized.
- Focus on plausible failure, not catastrophizing. The goal is not to generate every conceivable disaster. It is to surface the most credible paths to failure. Encourage specificity: not “something goes wrong with the technology” but “the API rate limits cause the product to fail under real user load.”
- Assign ownership to top risks. A pre-mortem that produces a list of concerns and no follow-up action is a wasted hour. Each significant risk identified should be assigned to someone who is responsible for either mitigating it or monitoring it.
Connecting the Pre-Mortem to Broader Thinking Tools
The pre-mortem sits within a family of reasoning strategies that deliberately introduce adversarial perspectives into decision-making. Inversion, a mental model associated with the mathematician Carl Jacobi and popularized by investor Charlie Munger, operates on the same logic: instead of asking how to succeed, ask how to guarantee failure, then avoid those things.
Red teaming is a related practice drawn from military planning, where a separate group is tasked with attacking a plan as aggressively as possible. The pre-mortem is a lightweight, accessible version of this — it does not require a separate team, just a temporary shift in perspective.
What all these tools share is a deliberate attempt to counteract motivated reasoning. Motivated reasoning is the tendency to evaluate evidence in ways that confirm what we already want to believe. When we are excited about a plan, we unconsciously discount evidence against it. These techniques create a structured moment where the opposite instinct — look for what is wrong — is explicitly rewarded.
Key Takeaway: What to Do Before Your Next Decision
The pre-mortem technique requires about thirty minutes and costs nothing except the willingness to hear uncomfortable answers. Here is how to apply it immediately.
- Before finalizing any significant plan or decision, call the relevant people together while the decision is still open.
- Give each person five to ten minutes to write independently, answering this prompt: “It is one year from now. This project has failed completely. Write down every reason you can think of that caused the failure.”
- Go around the room systematically. Each person shares one reason at a time. Record everything without debate or dismissal during this phase.
- Group the reasons by theme. Identify the three to five most credible and consequential failure modes.
- For each major risk, decide: Can it be mitigated now? Who owns monitoring it? Does it change the plan?
The goal is not to kill good ideas. It is to stop bad ones from hiding inside good-looking plans. The difference between a team that fails and a team that learns to avoid failure is usually not intelligence — it is whether anyone created the conditions for honest thinking before the money was spent.
Want to sharpen your thinking even further? Check out The Thinker’s Toolkit – our monthly membership of practical frameworks, worksheets, and a practice app to help you reason better, spot biases, and make smarter decisions.