Pre-mortem: pause at your most optimistic moment

Psychologist Gary Klein, in a short 2007 essay, proposed a simple but counter-intuitive move: before making a major decision, assume it has already failed — then ask why.

This sounds pessimistic, but it solves a real problem: once a team converges on a plan, they collectively go blind. Everyone sees the version where the plan succeeds. No one voices the "but" sitting in the back of their mind.

Why working backwards beats predicting forward

Ask a group "what could go wrong?" and answers stay abstract — execution might slip, the market might shift, competitors might react. These answers carry no weight.

Switch the question to "assume it's a year later and we failed completely — how does the story read?" — and the brain flips into specific-scenario mode. It generates identifiable, locatable failure paths. "We couldn't hire the key engineer." "Our anchor customer found out at month eight that we couldn't scale." "We dismissed that small competitor; six months later they shipped a cheaper version."

Concrete predictions are a hundred times more useful than abstract worry.

When to use it

• Before big-bet, hard-to-reverse decisions: fundraising, launches, signing contracts, marriage, buying a house
• When the team is enthusiastic and unusually unanimous — consensus is often a bias signal
• When you personally feel "this is going too smoothly"

When not to use it

Small reversible day-to-day choices don't need a pre-mortem — it becomes over-analysis. Pure exploration phases also don't fit, because there's no concrete plan yet to "fail."

A five-minute version

Next time you face a major decision, close the door:

1. Write the plan in one sentence
2. Assume it failed a year from now
3. List five specific reasons it failed — the more granular the better
4. Look at the list and ask: "Which of these am I least prepared to handle right now?"
5. Decide whether to proceed, modify, or restart

The full pre-mortem flow lives on Hone's framework page.