The Pre-Mortem: Why Imagining Failure Before You Start Is the Smartest Move

You've just green-lit a major project. The team is excited. The budget is approved. Everyone is optimistic. This is exactly when you're most vulnerable.

Psychologist Gary Klein developed the pre-mortem technique specifically for this moment. Unlike a post-mortem (which analyzes what went wrong after the fact), a pre-mortem imagines the project has already failed — and then works backward to figure out why.

How It Works

The process takes 30-45 minutes and works best with the full project team:

1. Set the scene: "Imagine we're one year in the future. This project has failed spectacularly. It's a total disaster."
2. Individual brainstorm: Each team member independently writes down all the reasons the project failed. No discussion yet. (2-3 minutes)
3. Share and compile: Go around the room. Each person shares one reason at a time. Continue until all reasons are listed.
4. Prioritize: Vote on which failure modes are most likely and most damaging.
5. Mitigate: For the top risks, develop specific prevention and contingency plans.

Why It's Better Than Traditional Risk Assessment

Traditional risk assessment asks "What could go wrong?" — which triggers optimism bias. People unconsciously downplay risks because they want the project to succeed. They also suffer from groupthink: once a leader expresses confidence, team members suppress their concerns.

The pre-mortem bypasses both problems. By assuming failure has already occurred, it gives people psychological permission to voice concerns. The framing shifts from "Why are you being negative?" to "Help us figure out what happened." Klein's research found that pre-mortems increase the ability to identify reasons for future outcomes by 30%.

Daniel Kahneman, who won the Nobel Prize for his work on cognitive biases, called the pre-mortem "the single most important piece of advice about decision-making that I can offer."

Real-World Impact

The US Army adopted the pre-mortem as part of its planning process after studies showed it caught critical risks that traditional planning missed — particularly "unknown unknowns" that teams hadn't even considered.

At Google, project teams run pre-mortems before major launches. In one notable case, a pre-mortem for a product launch revealed that the team had no contingency for a specific API partner going down. That partner did experience an outage during launch week, but because the team had already identified and mitigated this risk, the launch proceeded smoothly.

Hedge fund Bridgewater Associates uses a variant of the pre-mortem for investment decisions, systematically imagining how each position could go catastrophically wrong before committing capital.

Common Mistakes

• Not doing the individual brainstorm first. If you skip this and go straight to group discussion, you get groupthink — the exact problem you're trying to avoid.
• Stopping at identification. The pre-mortem is only valuable if you actually develop mitigation plans for the top risks.
• Doing it too early or too late. The sweet spot is after the plan is formed but before execution begins — when you know enough to identify specific risks but still have time to address them.

The pre-mortem costs almost nothing — just 30-45 minutes of the team's time. The alternative (discovering these risks during execution) costs orders of magnitude more. It's one of the highest-ROI thinking tools ever developed.