The Premortem
Before you launch, imagine the project has already failed catastrophically — then work backward to find the risks your team is currently blind to.
What it is
A Premortem inverts the usual project review. Instead of asking "what could go wrong," the facilitator declares the project has already failed, completely and publicly, some years from now, and asks the team to explain how. That small fictional distance is what makes it work: it swaps optimistic System 1 autopilot for a cold System 2 audit while the outcome is still safe to discuss, because nothing has actually happened yet.
Where it came from
The method was developed by cognitive psychologist Gary Klein and popularized by Harvard Business Review. Daniel Kahneman has called it his favorite single tool for de-biasing a decision. It's used at the World Bank, and in "prospective hindsight" form at NASA and in complex healthcare rollouts, precisely because those are environments where optimism bias is expensive.
The evidence
Studies on prospective hindsight — imagining an outcome has already occurred, then explaining it — show it raises a team's ability to correctly identify the causes of a future outcome by roughly 30% compared to a standard risk assessment.
Run the safeguard check first
The single most common way a Premortem fails is running it in a room where people don't feel safe naming the real risk. Before you schedule one, run this 5-question survey anonymously (1 = strongly disagree, 5 = strongly agree):
- If you make a mistake on this team, it is rarely held against you.
- People here can raise problems or tough issues without fear of blame.
- No one on this team acts to undermine or discredit a colleague's efforts.
- It is safe to take a calculated professional risk on this team.
- No one would ridicule someone here for voicing a dissenting opinion.
Don't run an open-room session — people will hide real risk to protect themselves. Use the Anonymous Inbox variant below instead.
Clear to run a standard, collaborative, open-room Premortem.
How to run it
1. Set the premise
Read this to the room: "Imagine we are three years into the future. Despite all our excitement, budget, and hard work, this project has failed catastrophically, completely, and publicly. For the next ten minutes, work in absolute silence and write a comprehensive history of exactly how and why we failed."
2. Silent, individual brainstorm
Every team member fills out their own grid, alone, across four categories: operational & tech, market & customer, team & culture, and external threats. No talking during this phase — that's what protects the quieter, more honest answers.
3. Consolidate and assign action
Share the points, group them by theme on a shared board, then take the top three and assign each one a preventative action, an owner, and a deadline.
4. Lock it in within 24 hours
Send a short follow-up naming the top threats, the action, the owner, and the date, and check on it at your normal weekly sync — a Premortem that isn't followed up becomes a slide nobody re-reads.
If your safety score came back low
Don't cancel the exercise — change the format. Set up a completely anonymous digital submission link and ask: "If you were secretly forced to bet $1,000 that this project will fail, what specific flaw would you bet on?" The facilitator reads the anonymous answers aloud during the session, which shifts the focus from who said it to whether the risk is real.
Where it breaks
Left untimed, a Premortem tips into analysis paralysis and over-inflated minor risks. Cap the silent-brainstorm phase at ten minutes and chair the consolidation strictly.