How to run a post-mortem that changes behavior, not just documents the incident.
Short answer
A post-mortem is a structured review run after a significant incident, failure, or project completion. It runs 60–90 minutes and follows five steps: build a shared timeline, identify contributing factors, find root causes (Five Whys or fishbone), write actionable preventions, and assign owners with deadlines. The goal is systemic improvement — not blame.
Post-mortems that produce real change share one trait: they separate what happened from who did it. The moment you attach blame, the conversation shifts from learning to defense.
Part 1 — Timeline reconstruction (20–30 min). Start with raw facts: what happened, when. Use a horizontal timeline on the whiteboard. Mark key events with timestamps. Every person in the room contributes what they observed from their vantage point. Do not editorialize — only facts belong on the timeline. Common discovery: the team often realizes there were multiple decision points where the outcome could have changed, and that systemic factors (not individual failures) shaped each decision.
Part 2 — Contributing factors (15–20 min). Ask: "What conditions made this failure more likely?" These are not causes — they're environmental factors: time pressure, unclear ownership, missing monitoring, miscommunication. List them separately from the timeline. Contributing factors are often systemic and worth addressing even if you can't trace a direct causal line.
Part 3 — Root cause analysis (20–25 min). Pick the top 2–3 contributing factors and apply Five Whys: ask "Why did this happen?" five times in succession. Each "Why" should produce a cause that's more fundamental than the one before. Stop when you reach a systemic root — an organizational structure, a process gap, or a design flaw — not an individual mistake.
Alternate format: fishbone diagram (Ishikawa). Draw a fish spine on the whiteboard. The head is the incident. Branches are categories (People, Process, Technology, Environment). Sub-branches are contributing factors under each category. Fishbone is better for complex incidents with multiple parallel cause threads.
Part 4 — Action items (15–20 min). For each root cause, write one or more preventive actions. The test: is this specific enough that we can check whether it was done? "Improve communication" fails the test. "Add a shared runbook with an owner-check step before any production deploy" passes. Aim for 3–7 actions total; more than that and none get done.
Part 5 — Assign and close (10 min). Name an owner and deadline for each action item. Read them back. The post-mortem report should be published within 24–48 hours — not weeks later when details are fuzzy.
Snap the whiteboard with BoardSnap. The AI reads the timeline, cause clusters, and action items and produces a structured post-mortem summary with a tri-state action list — open, in-progress, done.
Frequently asked
How soon after an incident should you run a post-mortem?
Within 3–5 business days. Any longer and the details fade. Any sooner and the team may still be in firefighting mode. For severe incidents, a quick 30-minute "hot debrief" within 24 hours captures raw observations before they're forgotten, with a full post-mortem following in 3–5 days.
Should a post-mortem be blameless?
Yes — and "blameless" doesn't mean consequence-free. It means the investigation focuses on systemic factors, not individual fault. When people know they can be honest without personal repercussions, you get better data and better mitigations. The blameless post-mortem is the standard practice at most mature engineering organizations.
What's the difference between a post-mortem and a sprint retro?
A post-mortem is triggered by a specific incident or failure and focuses on root cause analysis. A sprint retro is a scheduled cadence meeting at the end of every sprint focused on team process improvement. They use overlapping techniques (Five Whys, action items with owners) but serve different triggers and timeframes.
See it work in ten seconds.
BoardSnap is free on the App Store. Snap a board — get a summary and action plan.