The Pre-Mortem: How to Stress-Test a Decision Before You Make It

The review that comes too late

Most teams are good at post-mortems. After the launch misses, after the hire does not work out, after the acquisition disappoints, everyone gathers to explain what went wrong. The conversation is usually honest and occasionally useful. It is also, by definition, too late. The money is spent, the time is gone, and the option you rejected is no longer available.

A pre-mortem flips the timing. Instead of reviewing a failure that happened, you review a failure that has not happened yet. You do not ask "could this go wrong?" You say, plainly, "it is twelve months from now and this decision failed. Write the story of why."

The difference sounds cosmetic. It is not. "Could this go wrong" invites politeness: people mention a risk, everyone nods, the group moves on. "It failed — why" invites specifics. The mind is remarkably good at explaining a concrete outcome it has been told is real. That is the lever.

Why prospective hindsight works

Psychologists call it prospective hindsight: imagining an event as having already occurred. In a well-known study, groups that were told an outcome had happened generated about thirty percent more reasons for it than groups asked to estimate whether it might happen. The mechanism is simple. When a future is hypothetical, you sample it lightly. When it is described as a fact, you explain it, and explanation reaches for causes a possibility-check never would.

The founder of the method, Gary Klein, developed it after noticing that experienced decision-makers were rarely surprised by failures they had already imagined. The point is not pessimism. The point is that your brain already contains most of the risk model. The pre-mortem just gives it permission to speak before the decision is locked in.

There is a social benefit too. In most planning meetings, the person raising a doubt is implicitly disagreeing with the person who proposed the plan. That is expensive, so doubts go unspoken. A pre-mortem changes the framing: everyone is now asked to imagine failure, so raising a risk is cooperation, not opposition. The quietest person in the room often has the sharpest list.

Running a pre-mortem in twenty minutes

You do not need a facilitator, a workshop, or a full afternoon. The core protocol fits in twenty minutes and scales from a solo decision to a room of eight.

1. Set the scene (2 minutes). State the decision and the timeframe. "We are deciding to hire a head of sales. It is twelve months from now. The hire failed." Be specific about what "failed" means — not vague disappointment, but a concrete outcome: they left, the pipeline did not grow, the team turned over, the board lost confidence.

2. Generate reasons independently (7 minutes). Each person writes as many reasons as they can, silently, without discussion. Silent generation matters: if the first person to speak names the obvious risk, everyone else anchors on it and the list shrinks. Aim for quantity. Ten to twenty reasons is normal for a real decision.

3. Share and cluster (6 minutes). Go around the room, one reason per person per turn, until the lists are exhausted. Write every reason on the board. Then group the reasons into themes — hiring process, market timing, incentives, communication, resourcing, and so on. Naming the themes is how you turn a pile of worries into a risk model.

4. Prioritize and assign (5 minutes). Score each theme for likelihood and impact. Pick the top three. For each, name one concrete action that reduces the risk now, or one early-warning signal that tells you the risk is materializing. A pre-mortem that produces a list but no action is theater, not risk management.

The solo version

If the decision is yours alone, the protocol still works, with one adaptation: you need to defeat your own anchoring. Write the reasons in one sitting, then leave the list alone for a few hours or overnight before you prioritize. Your second reading will add the risks your first pass suppressed, because your mind has had time to stop defending the choice.

A second solo technique is to argue the opposite role on paper. Write a paragraph as the person who thinks your decision is a mistake. Not a strawman — the strongest version. If you cannot write that paragraph, you do not yet understand the decision well enough to make it. This is the same disconfirmation muscle that separates careful deliberators from confident ones.

Turning risks into early warnings

The most useful output of a pre-mortem is not a longer risk list. It is a set of tripwires: observable signals that tell you, in advance, which failure story is starting to come true.

Failure theme	Early warning signal	Predetermined response

---	---	---

Wrong hire	First two deliverables slip, or peers stop routing work to them	Structured 30-day review with named criteria

Market timing	Two consecutive weeks of flat demand after launch	Pause spend, revisit the launch window

Hidden dependency	A single vendor or person is on every critical path	Build a second path before scaling

Quiet dissent	Decisions get re-litigated after every meeting	Reopen the decision once, in writing, then close it

Scope drift	The definition of success changes twice without a new decision	Freeze the metric for one review cycle

Tripwires work because they move the argument to a moment when you are not emotionally invested in the outcome. When the signal fires, you follow the response you agreed to while calm. Without them, you will explain the signal away — that is what defending a decision looks like.

Four ways pre-mortems go wrong

They become complaint sessions. If the exercise turns into a list of grievances about the organization, stop and refocus on this decision. The unit of analysis is the choice, not the culture.

They are run after the decision is effectively made. If leadership has already announced the path, the pre-mortem becomes theater. Run it before the commitment, or do not run it at all.

Nobody owns the follow-through. The top risks need owners and dates. An unassigned risk is a note, not a mitigation.

The list is treated as a prediction. A pre-mortem is not a forecast. It is a search for fragility. You are not trying to predict which failure will happen; you are trying to make the decision robust to several of them at once.

Where it fits in a decision system

A pre-mortem is a stress test, not a decision rule. It pairs naturally with a decision journal: the pre-mortem generates the risks, and the journal records which ones actually appeared. Over six months, that pairing teaches you something no single decision can — which of your failure stories are real and which are noise.

It also pairs with classification. A reversible, low-stakes decision does not need a full pre-mortem; decide, observe, adjust. An irreversible one — a hire, a lease, a large commitment, a public promise — is exactly where twenty minutes of imagined failure pays for itself many times over.

The measure of a good decision is not that it avoided all risk. It is that you walked into the risk with your eyes open, and built the tripwires that let you change course early. A pre-mortem is how you get those eyes.

Your own decision pattern shapes which risks you naturally see and which you systematically miss. The free TangoEra check takes about a minute and maps how you weigh downside, timing, and uncertainty before you commit to a path.

A one-page template

If you remember nothing else, keep this:

• The decision, in one sentence, and the date it becomes irreversible.

• The failure story: it is twelve months later and this failed, because…

• The top three themes, each with a likelihood and impact score.

• One action and one early-warning signal per theme.

• The review date, written down now.

Run it before the commitment, not after. The best time to find a failure is while it is still imaginary.

Want the quicker read first? The Decision Snapshot is free ($0) — three questions, three minutes, a one-page read.

Want to shape what gets built next? TangoEra runs new tools with a small group of beta testers before release.