The post-mortem structure, slide by slide
Borrowed from the Apollo 13 incident review structure. Each beat is one slide, three at most.
- 01 CoverIncident name, detection time, severity, status, and the words "blameless review".
- 02 SummaryWhat happened, impact, root cause, resolution: four lines an executive can read in thirty seconds.
- 03 ImpactLead with the outcome that matters most, then what it cost, in one hero number and a quiet row.
- 04 TimelineEvery event with a timestamp, scrubbable, color-coded by phase.
- 05 DetectionTime to detect, diagnose and mitigate, plus every earlier signal you missed.
- 06 ResponseWhat the team did to stop the bleeding, in the order it happened.
- 07 Key mitigationThe one fix that saved you, shown working against its limit.
- 08 Root causeFive whys, from the symptom to the decision that made it possible.
- 09 RetroWhat went well, what went wrong, and where you got lucky, three items each.
- 10 Action itemsEvery fix with one owner and a type: prevent, detect, mitigate, process, learn.
- 11 Follow-upsStatus, then dated follow-ups, so the review ends on what happens next.
- Use it when
- After an incident, a launch, or a project that ended, good or bad.
- Typical length
- 8 to 12 slides.
- Format
- Sent as a written record, then presented to agree the actions.
See it in a real deck
Apollo 13, The incident review, 1970. Houston, we've had a post-mortem. Every slide opens our playable rebuild right where it is.
-
01Houston, we've had a post-mortem. -
02One tank failed. Three crew came home. -
03We lost the landing. We kept the crew. -
04143 hours, logged to the second. Scrub any of them. -
05We detected the failure in 27 seconds. The odd reading came nine hours sooner. -
06The lander became the lifeboat. -
07Spare filters: square. Sockets: round. -
08Five whys, from the bang back to a 1965 spec change. -
09Some of it was skill, some of it was process, and some of it was luck. -
10Nine recommendations. Every one has an owner. -
11Status: resolved. Crew: home.
More post-mortem examples
What good post-mortem decks do
- Blameless: systems and decisions, not people.
- Summary and impact first, then a timeline logged to the minute.
- Separate detection, response, and root cause; ask why five times.
- Name what went well, what went wrong, and where you got lucky.
- Every action item has an owner and a date.
Where post-mortem decks usually fail
- Blaming a person
- A root cause that stops at the first why
- Action items with no owner
Common questions about the post-mortem
What should a post-mortem include?
A summary of the impact, a timeline of what happened, the causes, what went well, what did not, and the actions that will prevent a repeat, each with an owner and a date.
What is a blameless post-mortem?
One that treats mistakes as the product of systems and pressures rather than individual failings, so people share what really happened and the fixes target the cause.
What is the difference between a post-mortem and a retrospective?
A retrospective is a regular check-in on how a team works. A post-mortem follows one event, usually something that went wrong or a project that ended.
Make yours with this structure
Type your site and we'll write the prompt for your deck, in your brand, built on the Apollo 13 incident review structure.
Building it with AI? Compare the ways to make it with Claude, or add Pitch Unfairly to ChatGPT or Codex.