When to use it
Use before a significant commitment — launching a product, hiring, investing, kicking off a project. Most valuable when the team is too aligned and risks aren't being surfaced.
Core tool in The Test when you need to break something before building it.
How it works in The Studio
Here's how a session works with WAiDE:
Sample output
Here's what a Pre-Mortem looks like in practice:
| Risk | Likelihood | Impact | De-risk |
|---|---|---|---|
| Key engineer quits before launch | High | Critical | Cross-train now, document architecture |
| Enterprise customers need SSO we don't have | Medium | High | Interview 3 target customers this week |
| Pricing too low for enterprise, too high for SMB | Medium | High | Run 5 pricing conversations before setting |
| Marketing launch falls flat — no one notices | High | Medium | Pre-sell to 10 beta users, get testimonials first |
| We built for a problem that isn't urgent enough to pay for | Medium | Critical | Test willingness-to-pay before building |
What you get
Prioritised list of top risks plus the cheapest way to de-risk each one before resources are committed. Often surfaces risks nobody had articulated openly.
Foundation
Developed by Gary Klein, cognitive psychologist, in 1989. Published in Harvard Business Review (2007). Taught at Harvard Business School, INSEAD, and Stanford GSB. Used by Amazon, Google, and McKinsey.
Why it works
The Pre-Mortem works through a cognitive mechanism called prospective hindsight. Research by psychologist Gary Klein, who developed the technique, shows that imagining an event has already happened increases our ability to identify reasons for that outcome by about 30% compared to forward-looking probability assessments. The simple act of treating failure as a fait accompli bypasses the optimism bias that makes teams underestimate risk.
Most risk management processes fail because they're run by people with a stake in the project succeeding. Nobody wants to be the person who raises the hard question in a planning meeting. The Pre-Mortem creates psychological safety by making pessimism the assigned task — everyone is expected to generate failure causes, so nobody feels like they're undermining the team by naming a real concern.
The technique is most powerful immediately before commitment — when the plan is solid enough to be real, but before resources are locked in and sunk cost starts protecting bad decisions. Too early and there's not enough to critique. Too late and people won't say what they actually think.
What to do with the output: the highest-priority risks become early warning indicators, not immediate fixes. Assign one owner per top-three risk. Name the earliest observable signal that this risk is materialising. Check those signals monthly — not as a post-mortem, but before the mortem happens.
Frequently asked questions
How is a Pre-Mortem different from a risk register?
A risk register catalogues known risks, usually by people with a stake in the project succeeding. A Pre-Mortem uses prospective hindsight — imagining failure has already happened — which psychologically frees people to say what they actually think. Gary Klein's research shows this method surfaces around 30% more risks than traditional forward-looking brainstorming.
When is the best time to run a Pre-Mortem?
Just before commitment — when the plan is solid enough to be real, but before resources are locked in. Too early and there's not enough specificity to critique well. Too late and sunk cost starts to suppress honest risk assessment. The ideal window is 'we're about to say yes to this.'
Can I run a Pre-Mortem solo, without a team?
Yes. WAiDE will play multiple perspectives — challenger, critic, market sceptic — raising scenarios you might not have considered. Solo pre-mortems are particularly useful for founders who don't yet have a team and need to stress-test a plan before pitching or committing.
What's the difference between a Pre-Mortem and Devil's Advocate?
A Pre-Mortem is scenario-based — you imagine a specific failure and work backward from it. Devil's Advocate is argument-based — you systematically attack the logic and assumptions of your idea. They complement each other well: Pre-Mortem surfaces risks, Devil's Advocate tests reasoning. Run Pre-Mortem first.