The Pre-Mortem — Imagine Your Decision Already Failed

Most teams plan a decision by listing the reasons it will succeed. The pre-mortem turns that around: assume the project has already failed catastrophically, then ask why. The unstated worries that polite meetings suppress come out within minutes — and the plan that emerges is usually a meaningfully better one.

The technique was popularised by cognitive psychologist Gary Klein in a 2007 Harvard Business Review article. Daniel Kahneman has since called it one of his favourite debiasing tools, citing it directly in Thinking, Fast and Slow. The reason it works has a name in the psychology literature: prospective hindsight.

A pre-mortem is a structured exercise run before a decision is finalised. The team is told to assume the project has already gone live and produced a disastrous outcome. Each person then privately writes a short story explaining what caused the failure. The lists are pooled and discussed.

This sounds trivial. The interesting part is what it surfaces. In a normal planning meeting, dissenters often stay quiet — disagreeing with a decision the boss has clearly endorsed feels socially expensive. A pre-mortem inverts the social dynamic. The exercise asks for criticism. People who would have privately doubted the timeline, the supplier, or the assumed customer demand now have permission to voice it.

Klein has described pre-mortems as a way to legitimise dissent. They treat scepticism as a contribution rather than an obstacle, which means the contribution actually arrives.

Klein is a cognitive psychologist best known for naturalistic decision-making research — how experts actually decide under time pressure, as set out in his 1998 book Sources of Power. He published the formal pre-mortem protocol in HBR in September 2007 under the title Performing a Project Premortem.

The psychological mechanism Klein draws on is older. In 1989, Mitchell, Russo, and Pennington published Back to the future: temporal perspective in the explanation of events in the Journal of Behavioral Decision Making. They showed that asking participants to imagine an event had already happened — rather than asking what might happen — increased their ability to identify plausible causes by roughly 30%. The shift in tense changes how the brain searches its memory: from a vague hypothetical to a concrete narrative.

Kahneman and Tversky's earlier work on the planning fallacy sets up why this matters. Teams systematically overestimate how quickly things will go well and underestimate how often things go wrong. A pre-mortem is one of the few interventions that has been shown to push estimates back towards reality without requiring people to override their natural optimism in the moment.

Three mechanisms do the work.

Prospective hindsight. When you imagine an outcome has already happened, you stop forecasting and start explaining. Explanations are more concrete than predictions, so the failure modes you generate are more specific and more useful. "Marketing might be late" becomes "the agency missed the launch deadline because the brief wasn't signed off until week six".

Reversed social pressure. In ordinary planning meetings, support for the leader's plan is the default. Pre-mortems flip the polarity: the entire room is now asked to argue for failure. Saying nothing in a pre-mortem is the conspicuous behaviour, not dissenting.

Independent generation. Klein's protocol asks people to write their failure stories silently and individually before any group discussion. This blocks two well-documented group failures: anchoring on whatever the first person says, and groupthink suppressing minority concerns. By the time the lists are read out, the room already contains a diverse set of independently generated risks.

Project management. A product team is about to commit to a six-month redesign. The pre-mortem prompt: "It's twelve months from now. The redesign launched, the bounce rate doubled, and the CEO has told us to roll it back. Why?" Plausible failure stories typically surface: the design was not tested with the segment that drives most revenue; the engineering team underestimated migration of legacy content; the launch coincided with a competitor's release; success metrics were not agreed before kickoff. Each story points to a concrete mitigation — a usability test before code, a content audit, a pre-defined rollback metric.

Investing. An investor is sizing a position in a single mid-cap stock. The pre-mortem prompt: "It's three years from now. The position lost 60% of its value. Why?" Common failure modes: the thesis depended on a single regulatory outcome that didn't land; management changed and capital allocation deteriorated; a customer concentration risk that wasn't priced; macro conditions shifted in a way the base rate would have predicted but the optimistic case ignored. Several of these connect directly to expected-value thinking — they re-weight the downside scenario that the original analysis under-counted.

Startup product launch. A founding team is preparing to ship a new SaaS product. The pre-mortem prompt: "Eighteen months in. We've burned through the round, ARR plateaued, and we're winding down. Why?" Failure stories tend to cluster around: the wedge use case was real but too narrow to grow; sales cycle was longer than the runway assumed; the founder spent most of their time on engineering instead of distribution; an enterprise feature shipped that no buyer asked for. The mitigations rarely change the headline strategy. They change which milestones the team commits to and how quickly capital is deployed.

A post-mortem looks at a project that has actually failed and asks why. It is essential — but it has two limitations. First, it happens after the cost is already paid. Second, it is contaminated by hindsight bias: once you know the outcome, the causes feel obvious, even when they were genuinely unforeseeable in advance.

A pre-mortem keeps the analytical structure of a post-mortem and moves it to a point where the findings can still change the plan. The team gets the diagnostic value without the irreversible loss. Pre-mortems and post-mortems are complementary: run the pre-mortem before launch, run the post-mortem after, and feed any lessons into the next pre-mortem template.

Treating it as a blame exercise. The room must understand that this is a hypothetical, not a referendum on the leader. If sponsors get defensive, the criticism that needs to come out won't.

Skipping the silent writing phase. Once anyone speaks, everyone anchors. The independent generation step is what produces a diverse list of risks — collapsing it into open discussion early throws away the main benefit.

Generating risks but not acting on them. A list of failure modes that doesn't change anything is worse than no list at all — it gives the team the feeling of having addressed risk while leaving the plan untouched. Each significant risk should map to a mitigation, an accepted trade-off, or an explicit kill criterion.

Inviting only the inner circle. The most useful failure stories often come from people closest to execution: the engineer who knows the migration is brittle, the rep who knows the client base. Excluding them turns the pre-mortem into a managerial echo chamber.

Pre-mortems are valuable when a decision is large, partially reversible, and made under uncertainty. They are overkill — and can be obstructive — when the decision is small, easily reversed, or genuinely time-critical.

They are also weaker for decisions where the bottleneck is information rather than judgement. If your team genuinely doesn't know whether the underlying market exists, a pre-mortem will surface the question but won't answer it. The right response there is a small, real test: a customer interview, a paid pilot, a prototype. The pre-mortem helps you decide which tests to run, not whether to run them.

A pre-mortem is one of several tools that push decision-makers from optimistic point estimates towards a more honest distribution of outcomes. Expected-value reasoning forces you to weight outcomes by probability. Second-order thinking forces you to consider downstream consequences. The pre-mortem complements both: it improves the inputs by surfacing failure paths that optimistic planning suppresses.

Kahneman explicitly framed the pre-mortem as a debiasing tool against the planning fallacy and excessive optimism. Used regularly, it tends to make teams more calibrated about timelines, budgets, and risk-adjusted upside. It does not eliminate uncertainty — but it makes the uncertainty that matters legible enough to plan around.