Run a Pre-Mortem: How to Kill Launch Risks Before They Kill You
A pre-mortem assumes your launch already failed and asks why, surfacing the risks confident planning meetings miss. Here is how to run one and turn it into a living risk radar.
Imagine the Launch Already Failed
Most launch reviews ask whether the plan is good. A pre-mortem asks a better question: it is six months from now, the launch was a disaster, what went wrong. By assuming failure has already happened, you give people permission to voice the doubts they would otherwise keep quiet, the ones that turn into post-mortem findings nobody flagged in time.
The technique comes from research by psychologist Gary Klein, and it works because prospective hindsight, imagining a future event as if it already occurred, makes people dramatically better at identifying reasons something will fail.
Why Pre-Mortems Beat Optimistic Planning
In a normal review, raising a risk feels like being the person who is not a team player. In a pre-mortem, the entire exercise is to find what kills the launch, so surfacing risk becomes the cooperative move rather than the disloyal one. This single reframe is why pre-mortems consistently catch risks that confident planning meetings miss.
How to Run One in 45 Minutes
The format is deliberately simple:
- Set the scene: state plainly that the launch failed badly, and ask everyone to write down why, silently, for five minutes.
- Collect every reason: go around the room and capture each failure mode without debate. Silence and independent writing first prevents the loudest voice from anchoring the room.
- Cluster and rank: group the failure modes and rate each on likelihood and impact.
- Assign owners: for the top risks, name a specific person and a specific mitigation. A risk without an owner is just a worry.
Turn the Output Into a Living Risk Radar
The mistake is treating the pre-mortem as a one-off cathartic session. The real value is the list of ranked, owned risks, which should live somewhere the team checks as the launch approaches, not in a doc that closes when the meeting ends. A risk radar that tracks each failure mode, its owner, and its status, the way Specky.space supports, keeps the pre-mortem honest right up to launch day.
Keep reading
Is Your AI PM Tool EU AI Act Compliant? A Framework for Product Managers
Every AI tool in your stack now has to answer this question. Here is the 4-step framework we used to answer it honestly for Specky, and how to run it on your own stack in under an hour.
Customer Journey Mapping for Product Managers: Stop Guessing, Start Seeing
Most customer journey maps end up as beautiful wall art that nobody opens after the workshop. Here's how to build one that actually drives product decisions.
The PM's Weekly Review: A 30-Minute Ritual That Replaces 5 Meetings
Most PMs are drowning in sync meetings that produce no decisions. Here is the 30-minute weekly review ritual that gives you the situational awareness of five meetings in one focused session.