Why hindsight works better in advance
The pre-mortem, developed by the research psychologist Gary Klein, inverts the standard risk discussion. Instead of asking what could go wrong (a question that invites polite, hedged answers), it asks the team to assume the decision has already failed spectacularly and to explain why. This use of prospective hindsight changes what people are willing to say. In a normal review, naming a fatal flaw sounds like disloyalty to a plan the room has worked on for months; in a pre-mortem, generating failure causes is the assignment. Dissent that meeting dynamics normally suppress becomes, for one hour, the measure of a good contribution.
Running one properly
The mechanics matter more than they look. A pre-mortem run as an open discussion collapses back into the very meeting it was designed to escape.
- Set the frame precisely: it is two years from now, the decision went ahead, and it has failed badly. Certainty of failure, not possibility, is what licenses candour.
- Silent, written failure stories first. Each person writes independently before anyone speaks, so the sponsor's view cannot anchor the room.
- Collect one cause per person per round until the list is exhausted. No rebuttals while collecting.
- Rank causes by plausibility multiplied by addressability: a likely failure you can act on outranks a dramatic one you cannot.
- Close by giving each retained cause an owner and a test. A pre-mortem that ends at the list has produced anxiety, not protection.
A worked structure
| Stage |
What happens |
What it protects against |
| Frame the failure |
The facilitator declares the decision dead: implemented, and failed badly |
Hedged answers written for the sponsor's comfort |
| Silent writing |
Everyone drafts their failure story alone, in full sentences |
Anchoring on the first or most senior voice |
| Collection round |
Each person reads one cause per turn until all are on the board |
The loudest three participants setting the agenda |
| Ranking |
Causes scored on plausibility and addressability, not on comfort |
Effort flowing to vivid risks instead of likely ones |
| Ownership |
Every retained cause gets a named owner, a test and a review date |
A thorough list that changes nothing about the plan |
How pre-mortems get blunted
- Run after the decision is emotionally made. If the sponsor has already announced the direction internally, the exercise generates footnotes, not challenge.
- Failure causes listed but never assigned owners, so the session substitutes for mitigation instead of producing it.
- The room self-censors because the sponsor is present and visibly invested. Attendance is not neutrality; some pre-mortems need the sponsor to leave.
- The stories converge on external causes (the market, the regulator, bad luck) because internal causes come with names attached.
Where independent operators sharpen it
A pre-mortem run internally is limited to the failures the team can imagine, and teams reliably imagine the failures they have already survived. Selected senior operators who have made the same category of commitment write failure stories from memory rather than imagination: the integration that stalled in month nine, the champion who left mid-programme, the saving that was real but arrived two years late. This is, in effect, what a structured client brief to the Global Board does professionally: a pre-mortem in which the failure stories come from people who watched them happen, and who carry no stake in this decision going ahead.
