The pre-mortem: how to stress-test a decision before you make it

The plan everyone agreed with

The most dangerous moment in a leadership team is not the heated argument. It is the easy yes. A proposal lands, the logic holds, heads nod, and the decision gets made before anyone has said the quiet thing they were thinking. Six months later, when the project is over budget and behind schedule, the same people can list exactly why it went wrong, often in detail. They knew. They just never said it out loud while it still mattered. The pre-mortem exists to drag that knowledge into the room before the decision is committed, not after.

Why optimistic planning fails

Most planning runs forward and runs hopeful. You set the goal, map the steps, assign the owners, and the conversation is shaped, often without anyone noticing, by a shared interest in the plan succeeding. The people who proposed it want it approved. The people approving it do not want to look obstructive. Dissent, when it exists, gets softened into a question or swallowed entirely. This is not weakness of character. It is the ordinary social physics of a group that has started to converge.

The psychologist Gary Klein named the corrective and the research behind it. A pre-mortem, in Klein's account, is a prospective exercise: before a decision is finalised, you imagine yourself at a point in the future where it has already failed, comprehensively, and you ask everyone in the room to explain why. The technique was popularised more widely by Daniel Kahneman, who featured it in his 2011 book Thinking, Fast and Slow as one of the few practical debiasing moves a team can actually run. Kahneman's interest was specific. He argued that the main virtue of the pre-mortem is that it legitimises doubt. In a normal planning meeting, raising a concern marks you as the difficult one. In a pre-mortem, surfacing a reason for failure is the assigned task, so the person who spots the flaw is doing their job rather than spoiling the mood.

The mechanism is a deliberate flip of perspective. Asking "what could go wrong?" invites the team to defend the plan and produce a tidy list of manageable risks. Asking "it is a year from now and this failed badly, what happened?" does something different. It grants the failure as a fact and asks for the explanation. People who would never have voiced a worry will happily diagnose a corpse. The certainty in the framing gives them cover, and the cover is the whole point.

The pre-mortem as a decision under uncertainty

At CapabilityFX we treat every consequential decision as a bet placed under uncertainty with the information available at the time. That framing runs through how we think about decision-making under pressure, and it is what makes the pre-mortem more than a brainstorming trick. If a decision is a bet, then the job before you place it is to find the ways the bet loses that you have not yet priced in. Optimistic planning prices the upside. The pre-mortem prices the downside, and it does so while the stake can still be adjusted, hedged, staged, or declined.

There is a real limit on how much this helps, and it is worth being honest about. The research on the pre-mortem, including Kahneman's own caution, is clearer that it improves the surfacing of concerns than that it always improves the final outcome. A pre-mortem does not predict the future and it does not guarantee a better call. What it reliably does is widen the set of risks the team has actually considered and lower the social cost of naming them. That is a worthwhile gain on its own terms, and it is the gain you should expect, rather than a crystal ball.

Where it sits in the decision

The pre-mortem belongs to a discipline we keep returning to: building judgement that holds, rather than collecting more frameworks. The capability it draws on is not analytical horsepower. It is the willingness to invite an uncomfortable truth into the room and sit with it. That is the same inside-out capability that anchors the DUAL model, specifically the move from understanding a risk to genuinely accepting it rather than explaining it away. A leader who runs a pre-mortem and then quietly dismisses everything it surfaces has performed the ritual without doing the work. The technique only pays out for a leader who can actually hear that their preferred plan might fail, and act on it.

How to run one

The mechanics are simple, which is part of why they get skipped. A pre-mortem takes about an hour and slots in at the point where a decision is nearly made but not yet committed. Run it too early and there is no concrete plan to attack. Run it too late and the decision has hardened past the point of changing.

Set the scene honestly. Gather the people who will live with the decision, including the quieter ones whose doubts rarely make it into the minutes. State the plan as it currently stands, in one or two sentences everyone recognises. Then deliver the premise plainly: it is a year from now, we went ahead with this, and it has failed. Not stumbled, failed. The business case did not land, the rollout stalled, the numbers came in well under. That is fixed. Your job for the next ten minutes is to write down, privately and on your own, every reason that could explain it.

Write first, then speak. The silent independent step matters more than it looks. If you open with a group discussion, the first confident voice anchors the room and the rest of the list bends towards it. Two minutes of private writing before anyone speaks captures the concerns that the most junior or most cautious person would otherwise keep to themselves. This is the same principle that makes a well-run decision review work: separate the honest individual signal from the social pressure of the group before the two get tangled.

Pool, cluster, and prioritise. Go round the room and collect every reason without debate or defence at first. Cluster them. Then, for the handful that are both plausible and serious, do the actual work: what early signal would tell us this one is materialising, and what would we change now to reduce its odds or its cost? A pre-mortem that ends with a list and no decisions is theatre. The output is a short set of concrete adjustments to the plan, plus the one or two risks you have consciously chosen to carry with eyes open.

What it looks like in practice

A chief operating officer in a manufacturing group was weeks from signing off a new enterprise system. The business case was strong, the vendor was credible, and every steering meeting had ended in agreement. Before the final sign-off she ran a pre-mortem, framed exactly as failure: eighteen months on, the rollout has gone badly and we are quietly looking at alternatives. The private writing surfaced something the steering meetings never had. Three separate people, independently, named the same risk: the warehouse teams who would use the system daily had not been in a single design conversation, and the project assumed an adoption it had not earned. It had not come up before because raising it would have meant questioning a plan that senior people clearly wanted. The pre-mortem did not kill the decision. It changed it. The rollout was re-sequenced to bring the floor teams in early, and the risk that would most likely have sunk the project was priced in before a cent was committed.

A founder of a professional-services firm used a pre-mortem on a decision in the other direction: whether to turn down a large, high-profile client that everyone instinctively wanted to win. The optimistic case wrote itself, marquee logo, strong fee, a door into a new sector. He inverted it. Imagine we took this and, a year later, deeply regret it. The failure reasons came quickly once the framing made them safe to say: the scope was vague and the client had a reputation for moving the goalposts, the work would pull the two best people off the engagements that actually paid the bills, and saying yes would crowd out the kind of work the firm was trying to become known for. None of that had survived the earlier conversations, because turning down a name-brand client felt like a failure of ambition. The pre-mortem reframed it as a risk to be examined rather than a nerve to be tested. He declined the client. A year on, watching a competitor struggle with exactly the scope problems his team had named, he counted it as one of the better decisions the firm had made, and one it would not have reached by planning forward and hopeful.

In both cases the technique did the same thing. It gave permission to say the true and unwelcome thing while it could still change the decision, instead of after, when all that is left is to be right in hindsight.

The reader's next step

The fastest way to know whether your team needs this is to look at how your last few significant decisions actually got made.

Three questions to sit with

• When we last made a big call, did anyone in the room argue against it, properly? If your recent decisions have a suspiciously clean run of agreement, that is not a sign of good judgement converging. It is more often a sign that dissent never found a safe door, and the risks went unpriced.
• After our last project disappointed, how much of the cause had someone already suspected beforehand? Trace it honestly. If the post-failure analysis is full of things that were knowable and quietly known, your problem is not foresight. It is that nobody had a sanctioned moment to say it.
• Could the most cautious person in the room derail a plan I clearly favour, without it costing them? If you cannot picture that happening, the constraint is not your team's intelligence. It is the safety you are or are not creating, and a pre-mortem only works on top of that safety.

The pattern these questions reveal is the same one we work on across a leadership team rather than in a single meeting. Surfacing dissent on demand, pricing risk before commitment, and acting on what you hear are developable capabilities, not personality traits. Our use cases show what that kind of work looks like in applied settings, and the assessments we use help locate where a particular team's judgement holds and where it bends under pressure.

The two bookends of a decision

A pre-mortem is the discipline you run before you commit. Its complement is the post-decision review: the discipline you run after, to separate the quality of the bet from the luck of the bounce and learn from it honestly. Together they bookend a decision. The pre-mortem widens the risks you consider going in. The review tells you, coming out, whether the reasoning was sound regardless of how it turned out. A team that does both stops making the two most common mistakes at once: committing to plans nobody stress-tested, and learning the wrong lessons from how they happened to land.

Neither is a clever new way to decide. Both are cheap, repeatable habits that compound. If you want to think through how to build them into how your leadership team actually works, rather than running one good meeting and reverting, that is the conversation our services are built for, and you can start it with us.

The leaders described here are representative composites drawn from patterns we observe in practice, not identifiable individuals.