Pre-Mortems — the 15-Minute Ritual That Prevents Most Project Disasters
Post-mortems happen after the failure. Pre-mortems happen before — and Gary Klein's research shows they boost problem identification by 30%. The single highest-ROI meeting you can run.
- A pre-mortem flips the script: 'Imagine this project failed catastrophically — write the reasons why.'
- Klein's research: prospective hindsight (imagining failure) boosts cause identification by ~30% over open brainstorm.
- It bypasses confirmation bias and gets quiet skeptics to speak up.
- Costs 15–30 minutes. Use it for every Type 1 decision and every major launch.
- The output isn't a fear list — it's a prioritized set of risks with assigned mitigations.
Every team has a quiet person in the room who can see the iceberg. The pre-mortem is the meeting designed to make them speak.
How it works
Psychologist Gary Klein developed the pre-mortem in the 1990s. The frame is simple: assemble the team, present the plan, then ask everyone to imagine it's a year from now and the project has failed spectacularly. Each person spends five minutes silently writing down every reason that might have caused the failure. Then you go around the room and share.
Why it beats normal brainstorming
'What could go wrong?' is a defensive question. People hedge, soften, defer to the project owner. 'Why did this fail?' is a creative question. Once failure is the premise, the brain stops protecting the plan and starts generating reasons — including the ones political dynamics usually suppress.
The 5-step ritual
- 11. Frame the failure'It's 12 months from now. This launch was a disaster. Headlines are bad. Customers churned. What happened?'
- 22. Silent generation (5 min)Everyone writes their own list. No discussion. This protects against anchoring on the loudest voice.
- 33. Round-robin share (10 min)Each person reads one item. Go around until lists are exhausted. No debate yet — just capture.
- 44. Cluster and prioritizeGroup similar risks. Vote on the top 3 most likely-and-damaging.
- 55. Assign mitigationsFor each top risk, name an owner and a single concrete action this week to reduce it.
Have the most senior person in the room share their list last. If the boss goes first, you'll get five carefully-curated versions of the boss's list. Reverse the order and you'll get five genuine perspectives.
Do this Monday
- For your next launch, hire, reorg, or product bet — schedule a 30-minute pre-mortem before the kickoff.
- Include one person who is skeptical of the plan. Without dissent, you've just held a status meeting.
- Write the top 3 risks and mitigations into the project's working doc. Reference them at every milestone review.
- After the project ships, hold the actual post-mortem and check: how many predicted risks materialized? This calibrates the team for next time.
- Make pre-mortems mandatory for any Type 1 decision (see related). They're the cheapest insurance you'll ever buy.
“A premortem is the opposite of a postmortem. We pretend that a patient has died, and ask, 'What killed him?'”
- Performing a Project Premortem — HBR — Gary Klein, 2007
- Thinking, Fast and Slow — Daniel Kahneman, 2011
Read next
All playbooksJeff Bezos's most-cited framework: irreversible decisions deserve deliberation, reversible ones don't. Most organizations confuse the two — and pay for it in lost speed and bad outcomes.
Inversion. Second-order thinking. Opportunity cost. The handful of mental tools that turn ordinary judgment into strategic thinking — without requiring an MBA.
Every people decision you make is filtered through 200+ documented cognitive biases. You can't eliminate them. You can build processes that contain the damage.