Pre-Mortem Analysis
A Pre-Mortem is a structured exercise — pioneered by decision researcher Gary Klein and popularized by Daniel Kahneman — where, BEFORE a project launches, the team imagines it has failed catastrophically and works backwards to identify why. The frame is: 'It is 12 months from now and this transformation has been a complete disaster. Write the autopsy.' Klein's research showed that 'prospective hindsight' — imagining a future event has already happened — increases people's ability to correctly identify reasons for future outcomes by ~30% compared to standard risk identification. The exercise unsticks groupthink, creates psychological safety to voice doubts (because the failure is hypothetical), and surfaces risks that risk registers, RAID logs, and steering committee reviews systematically miss. Output is a ranked list of failure causes plus mitigations baked into the plan from day one.
The Trap
The trap is doing a pre-mortem as a checkbox exercise — 30 minutes at the end of a kickoff, facilitated by the project sponsor, with everyone politely listing 'scope creep' and 'change resistance.' That's not a pre-mortem; it's risk theater. A real pre-mortem requires: anonymous individual writing first (no group discussion until after), a facilitator who is NOT the sponsor (sponsors filter critique), 60+ minutes minimum, and explicit permission to be brutal. KnowMBA POV: post-mortems can only catalog what already broke; pre-mortems uncover what risk registers systematically miss because risk registers are written by the same people who built the plan. If your pre-mortem doesn't surface 2-3 things that genuinely surprise leadership, it wasn't a pre-mortem — it was a meeting.
What to Do
Run a pre-mortem after the plan is drafted but BEFORE it is approved. The protocol: (1) Frame: 'It is [end date]. The project failed catastrophically. We are doing the autopsy.' (2) Silent individual writing: 10-15 minutes, each participant lists every plausible cause of failure they can imagine. No talking. (3) Round-robin sharing: each person reads ONE cause at a time until all are surfaced — no debate, no defense. (4) Cluster and rank: group by theme, vote on top 5-7 most likely failure causes. (5) Mitigation design: for each top failure cause, design a specific mitigation, owner, and trigger metric. (6) Bake mitigations into the plan and the risk register. Re-run the pre-mortem at major milestones — risks shift as the project progresses.
Formula
In Practice
Gary Klein documented a pre-mortem at a Fortune 500 company planning a $50M ERP rollout. In the kickoff risk review, the steering committee identified standard risks: scope creep, vendor delivery, change resistance. In the pre-mortem (run by an external facilitator, anonymous writing), three risks surfaced that no one had voiced in the formal review: (1) the executive sponsor was rumored to be leaving, (2) the chosen vendor had failed at a similar implementation at a competitor (knowledge that two team members had but hadn't shared), and (3) the timeline assumed legacy data quality that the data team privately knew was fictional. All three risks materialized within 6 months. The pre-mortem identified them; the formal risk process didn't — because the formal process was led by people who didn't want to be seen as negative.
Pro Tips
- 01
Facilitator must NOT be the project sponsor or PM. Use a neutral third party — internal coach, external consultant, or a leader from a different function. When the sponsor facilitates, participants self-censor to avoid signaling 'I think your project will fail.'
- 02
Anonymous written input first, group discussion second. The single biggest failure mode of pre-mortems is jumping straight to group brainstorm — the loudest/most senior voice anchors the discussion and the unique risks people would have written privately never surface.
- 03
Run pre-mortems at TWO points: post-plan/pre-approval (catches plan flaws) and at the 30% completion mark (catches execution drift). Most teams run one and call it done; the second one catches a different class of risk.
Myth vs Reality
Myth
“Pre-mortems are just risk identification with a creative name”
Reality
Risk identification asks 'what could go wrong?' — an open-ended question that triggers cautious, hedged responses. Pre-mortem asks 'why DID this fail?' — a closed, specific question that triggers concrete causal explanations. Klein's research showed prospective hindsight increases correct identification by ~30%. The framing shift is doing the work, not the exercise label.
Myth
“Doing a pre-mortem signals lack of confidence in the project and demoralizes the team”
Reality
The opposite. Teams report higher confidence after pre-mortems because they've stress-tested the plan and built mitigations into it. Avoiding the pre-mortem signals fragility — a plan that can't survive imagined failure shouldn't be approved.
Myth
“If you have a robust risk register, you don't need a pre-mortem”
Reality
Risk registers and pre-mortems surface different risks. Registers catch known/cataloged risks (vendor delivery, budget overrun). Pre-mortems catch contextual/political/unspoken risks (sponsor instability, vendor reputation, data quality fictions). Sophisticated programs run both.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
You're about to launch a $20M digital transformation. The PM proposes a 60-minute risk workshop where the team brainstorms what could go wrong. What's the highest-leverage upgrade to make this a real pre-mortem?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Pre-Mortem Risk Identification Lift vs. Standard Risk Review
Project risk identification effectiveness across program typesKlein original research finding
+30% correct cause identification
Well-run pre-mortem (anon + external facilitator)
+25-35% lift
Mediocre pre-mortem (group brainstorm only)
+5-10% lift
Sponsor-facilitated 'pre-mortem'
0% lift (or worse)
Source: Gary Klein, Performing a Project Premortem (Harvard Business Review, 2007)
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Gary Klein / HBR Pre-Mortem Research
1999-2007
Decision researcher Gary Klein, drawing on his work with naturalistic decision-making in high-stakes environments (firefighting, military), developed and codified the pre-mortem method. His core insight: prospective hindsight — imagining an outcome has already happened — produces dramatically better causal reasoning than imagining what might happen. In controlled experiments and field studies across corporate, military, and intelligence contexts, Klein documented ~30% improvement in correct cause identification when teams used pre-mortem framing vs. standard risk identification. Daniel Kahneman cited the pre-mortem in 'Thinking, Fast and Slow' as one of the few debiasing techniques with consistent empirical support. Klein's Harvard Business Review article in 2007 brought the method into mainstream corporate strategy.
Klein research effect size
+30% correct cause identification
Time required (typical)
60-90 minutes
Adoption (Fortune 500)
Standard practice in high-stakes programs
Kahneman endorsement
Cited in Thinking, Fast and Slow
The pre-mortem is one of the few risk-identification techniques with peer-reviewed evidence behind it. The framing shift — 'why DID it fail?' vs. 'what could go wrong?' — is doing the heavy lifting. Adopt the framing or skip the exercise.
Decision scenario
The Skipped Pre-Mortem
You're the COO sponsoring a $40M ERP transformation. The PM has scheduled a 30-minute risk review at the end of the kickoff, with the steering committee. You've read about pre-mortems and suspect this won't surface the real risks. The PM argues 'we have a comprehensive risk register; the pre-mortem is duplicative.' The CIO is skeptical of 'imagination exercises' and wants to keep momentum.
Program budget
$40M
Planned duration
18 months
Current risk identification
RAID log + steering risk review
Pre-mortem proposed
No (PM resistance)
Sponsor (you) instinct
Risk register is too clean
Decision 1
You can either accept the PM's plan and move forward (preserving political capital and momentum) or insist on a real pre-mortem (60-90 min, external facilitator, anonymous writing, before plan approval). The pre-mortem will delay approval by 1 week and signal to the team that you don't fully trust the plan.
Accept the standard risk review. The risk register looks comprehensive, the team is excited, and a pre-mortem at this stage would create unnecessary friction and signal mistrust.Reveal
Insist on a real pre-mortem: external facilitator, 90 minutes, anonymous individual writing first, mitigation design as the output. Delay plan approval by 1 week. Frame to the team as 'we're stress-testing the plan, not the people.'✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Pre-Mortem Analysis into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Pre-Mortem Analysis into a live operating decision.
Use Pre-Mortem Analysis as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.