What is a pre-mortem — and why it catches the risks your planning missed.
Short answer
A pre-mortem is a structured risk-identification exercise where participants imagine a project has already failed badly, then work backward to explain why. Developed by psychologist Gary Klein, it uses prospective hindsight to surface risks that traditional risk planning misses. A pre-mortem typically runs 45–60 minutes and produces a ranked risk register with named mitigations — before the project launches.
The pre-mortem technique was developed by research psychologist Gary Klein and introduced in a 2007 Harvard Business Review article. The mechanism is prospective hindsight: research shows that people are significantly better at explaining why something already happened than at predicting what might go wrong in the future. By framing the project as having already failed, a pre-mortem unlocks this explanatory ability for failure scenarios that haven't occurred yet.
Why it works better than standard risk planning. Traditional risk planning asks: "What might go wrong?" This question is hard to answer honestly, because optimism bias leads teams to underweight unlikely but high-impact failures, and social pressure suppresses naming risks that might seem like criticism of leadership or the plan. The pre-mortem eliminates both problems by making failure the premise rather than the question.
The session. 45–60 minutes, run 1–2 weeks before a significant launch or decision. Participants write independently for 10 minutes, listing every reason the project failed — including ones that feel unlikely or uncomfortable to say out loud. Then they share, cluster, and vote on the most significant risks. The top risks produce mitigation plans with named owners.
Pre-mortem vs. risk review. A risk review asks "what are the risks?" in a meeting format, which typically produces a short list of obvious risks already on everyone's mind. A pre-mortem consistently produces longer, more honest lists — including political risks, dependency risks, and assumption risks that are usually too uncomfortable for a standard risk discussion.
When to run a pre-mortem.
- Before a product launch
- Before a major organizational change
- Before a significant strategic bet
- Before signing a contract or partnership
- Before a major conference or event
When not to run one. After the project is already underway and too late to course-correct — at that point, a different facilitation technique is more useful. Also not appropriate as a substitute for ongoing project monitoring; it's a one-time session, not a continuous practice.
After the pre-mortem, snap the whiteboard with BoardSnap. The AI reads the risk clusters, vote counts, and mitigation notes and produces a clean risk register ready for the project tracker.
Frequently asked
Who invented the pre-mortem?
Gary Klein, a research psychologist specializing in naturalistic decision-making, developed and named the technique. He described it in a 2007 Harvard Business Review article titled "Performing a Project Premortem." The underlying prospective hindsight concept was documented in academic research by Deborah Mitchell, Edward Russo, and Nancy Pennington in 1989.
How is a pre-mortem different from a post-mortem?
A pre-mortem happens before a project launches and asks: "Why did this fail?" in the imagined future. A post-mortem happens after a failure and asks: "Why did this fail?" in the real past. Both use similar techniques but serve different purposes: pre-mortems prevent problems, post-mortems analyze ones that already occurred.
Can a pre-mortem demoralize the team?
Done well, it doesn't — it increases confidence by demonstrating that risks have been identified and addressed. The framing matters: position it as a tool for making the project succeed, not as a signal of doubt. Teams that run pre-mortems consistently report feeling better prepared, not more anxious.
See it work in ten seconds.
BoardSnap is free on the App Store. Snap a board — get a summary and action plan.