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

All 108 frameworks
8.3BeginnerModule 08 · Decide with Confidence

Post-Mortem Review

Extract the full learning from every outcome - win or lose

The prompt

Copy & paste ready
8.3Post-Mortem Review
Act as a Post-Mortem facilitator. Project or event : [DESCRIBE WHAT HAPPENED] Outcome : [WHAT ACTUALLY RESULTED — METRIC, TIMELINE, QUALITY] Target : [WHAT WAS PLANNED OR EXPECTED] Team involved : [ROLES AND CONTRIBUTIONS] Structure a complete Post-Mortem: TIMELINE : Reconstruct the key events in sequence. When did things diverge from the plan? WHAT WORKED : 3 things that went well and why. What can be systematised from these? WHAT FAILED : 3 things that did not work and why. Use 5 Whys for the most critical failure. ROOT CAUSES : The underlying systemic reasons, not the surface events. ACTION ITEMS : 3 specific changes owner, deadline. For each: what process or system changes? KNOWLEDGE CAPTURED: One paragraph to add to our playbook. Post-Mortem Review 1 2 3 4 Capture the Ask What & Extract the Define Outcome Why Learning Action Items
LabelsReplace theseSwap the role below

LabelsReplace theseSwap the role below

Pro tip, from the book

The most valuable Post-Mortem output is the paragraph added to the playbook. Not the action items, those are often forgotten. A one-paragraph insight written while the memory is fresh and placed in a shared document creates institutional knowledge that survives team turnover. Build the habit of writing it before the meeting ends.

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

Your team debriefs informally after projects finish. The same mistakes recur because learning is not systematically captured or applied. Wins are celebrated without understanding what caused them. You are not compounding your experience.

How the framework works

From the printed page

A Post-Mortem is a structured review conducted after a project, campaign, launch, or significant event to extract learning and improve future performance. Unlike a blame session or a celebration, a well-run Post-Mortem is analytically neutral it asks what happened, why it happened, and what will be done differently next time. Amazon pioneered the blameless post-mortem culture in engineering; it applies equally to sales, marketing, product, and leadership decisions. AI can structure a complete Post-Mortem analysis when given the outcome data.

The method, in four moves

Do these in order
1

Run Post-Mortems on wins as well as failures - understanding what caused a win is equally valuable.

2

Schedule the Post-Mortem within 2 weeks of the outcome, memory degrades fast.

3

Focus on process, not people , a good Post-Mortem improves systems, not morale.

4

The output must include specific changes, a Post-Mortem without action items is a retrospective, not a review. "Blameless" doesn't mean consequence-free, it means the analysis targets the system, not the person. If your Post-Mortem drifts into naming who messed up instead of what broke, you've turned a learning tool back into the blame session it was designed to replace.

Where the framework comes from

Amazon engineering culture — blameless post-mortem · Agile retrospective 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.3 of 108
Printed onPages 189190
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