Page 188 · Module 08, Decide with Confidence · this screen continues that page

All 108 frameworks
8.2IntermediateModule 08 · Decide with Confidence

Pre-Mortem Analysis

Imagine it already failed then figure out why

The prompt

Copy & paste ready
8.2Pre-Mortem Analysis
Act as a Pre-Mortem facilitator. Project or decision : [DESCRIBE WHAT YOU ARE ABOUT TO DO] Timeline : [HOW LONG THIS WILL TAKE] Team involved : [ROLES RESPONSIBLE FOR EXECUTION] Resources committed : [BUDGET, TIME, PEOPLE] Run a Pre-Mortem: SCENARIO: It is [DATE 12 MONTHS FROM NOW]. This project has failed. Not partially, completely. What happened? Generate 10 specific reasons it failed, across: Execution failures (team, timeline, quality) Market failures (wrong assumptions about customers) Resource failures (budget, capacity, dependencies) Strategic failures (wrong direction or timing) External failures (competition, regulation, market shift) Then: rank the top 3 by likelihood × severity. For each top failure: one prevention action and one owner. Pre-Mortem Analysis Imagine Failure Write Individually Identify Top 3 Assign Prevention Project has failed one year Each person lists every Group finds the most likely, Each failure mode gets a from now reason it failed most serious failure modes named owner and action
LabelsReplace theseSwap the role below

LabelsReplace theseSwap the role below

Pro tip, from the book

The Pre-Mortem's greatest value is not the list of failure modes — it is the social permission it creates for people to raise concerns. In a team that is committed to a plan, raising doubts feels disloyal. The Pre-Mortem makes it the job. Run it before every significant commitment and watch concerns surface that would have stayed silent until they became problems.

Who should run this prompt

Module role profile

Who should stress-test your most important decisions? Most bad decisions were not obviously bad at the time — they had a good first-order case and a hidden second-order cost. The roles on this page are designed to surface what you cannot see from inside your own reasoning. Some will challenge your logic. Some will challenge your assumptions. One will challenge whether you are even asking the right question.

Choose any role to drop it into the prompt above. Only the highlighted opening clause changes — the rest of the prompt stays exactly as printed.

Internal rolesThink from inside the organisation
Outside perspectivesChallenge your blind spots

◆◆◆◆◆ → ◆ seniority, board level down to specialist outside the organisation

How to make any role sharper

  1. Add years of experience: "...with 15 years in enterprise SaaS" produces different depth than just the title.
  2. Add what they care most about: "You care most about [X]" shapes every word of the output.
  3. Add their communication style: "Be direct. Flag risks first. No jargon." changes the tone entirely.
See also: 1.3 Role Prompting - The Expert Chair

Use this when

The problem it solves

You are about to launch something, make a major hire, or commit significant resources and you want to stress-test it before you commit. But your team is optimistic and no one is raising the hard questions.

How the framework works

From the printed page

The Pre-Mortem was developed by psychologist Gary Klein as an antidote to groupthink and planning optimism. Before a project begins, the team imagines it is one year in the future and the project has failed spectacularly. Each person writes down every reason they can think of for why it failed. The group then reviews all reasons and identifies the most likely and most serious failure modes. Unlike a risk register (which asks 'what could go wrong?'), the Pre-Mortem asks 'what did go wrong?' the past tense activates a different and more honest mode of thinking.

The method, in four moves

Do these in order
1

Run the Pre-Mortem in writing first, verbal Pre-Mortems are dominated by the loudest voice.

2

Separate generation from evaluation, collect all failure reasons before discussing any of them.

3

Focus on the top 3 most likely and most serious failure modes, you cannot mitigate everything.

4

For each top failure mode, assign a specific owner and a specific prevention action. A pre-mortem that stays a discussion is wasted effort. If the top three failure modes don't end with a named owner and a specific prevention action, you've identified the risks and done nothing to stop them.

Where the framework comes from

Gary Klein, psychologist — Pre-Mortem methodology

When this page changes, your copy of the book does not have to.

The book prints the framework. This page keeps it — and keeps the prompt current, because prompting technique moves faster than print does. When it moves, this page is rewritten and the code in your copy keeps pointing at it. No second edition, no replacement purchase, no account.

If something here looks wrong — a prompt that does not match its framework, a figure that reads oddly — tell Raphy. That correction reaches every printed copy at once.

Framework8.2 of 108
Printed onPages 187188
Prompt extracted18 Sept 2026
Costs to readNothing, no account

Copying is free. An account keeps them.

Nothing on this page is behind a login and nothing ever will be. Save any prompt to your own list, pick up on another device, and send a colleague a link with your name on it. No card, no trial, no paywall on the prompts themselves.

See how it works
Save this framework to your own list
Pick up where you left off on another device
Send a colleague a link with your name on it