Framework

Pre-mortem vs. Post-mortem: Key Differences & Examples

Pre-mortem vs. post-mortem: run a pre-mortem before launch to surface risks, and a post-mortem after to find root causes. Side-by-side table and real example.

King MarkLast reviewed 5 min read

A pre-mortem (or premortem) and a post-mortem (or postmortem) work backwards from failure at opposite ends of a project. In practice, a pre-mortem is the operational opposite of a post-mortem: one prevents failure before a launch or commitment, while the other investigates what actually broke afterward.

At a glance: Pre-mortem vs. Post-mortem

Pre-mortemPost-mortem
TimingBefore work starts or a project shipsAfter an incident, missed milestone, or shutdown
Core question"Imagine this failed completely — what caused it?""It failed. What actually happened and why?"
EvidenceHypothetical risks, domain knowledge, assumptionsLogs, metrics, customer interviews, timeline
OutputRanked risks, plan edits, owners before launchRoot-cause analysis + systemic action items
Emotional loadLow — nothing has broken yetHigh — real losses and defensiveness
OriginGary Klein, The Power of Intuition, 2004 (popularized in HBR, 2007)Engineering, aviation, and medicine (Google SRE postmortem culture)

Pre-mortem vs. post-mortem vs. retrospective

Teams also confuse post-mortems with sprint retrospectives. All three review failure or friction, but their triggers and outputs are distinct:

RitualTriggerFocusPrimary artifact
Pre-mortemHigh-stakes upcoming commitmentProspective failure modes in a planPre-launch mitigations and kill criteria
Post-mortemSpecific outage, miss, or shutdownVerified root causes and contributing factorsBlameless timeline + preventative fixes
RetrospectiveFixed cadence (end of sprint or quarter)Everyday team workflow and morale1–3 process experiments for the next cycle

When to use a pre-mortem

Use a pre-mortem when a decision is costly to reverse and the team has been building forward for weeks or months, creating optimism bias around the plan.

Typical triggers:

  • 2–4 weeks before a major product launch or pricing change
  • Kickoff of a multi-quarter migration or replatforming
  • After a strategy decision, before budget and headcount lock
  • Late-stage M&A or major vendor commitment

Pre-mortem template and step-by-step guide →

When to use a post-mortem

Use a post-mortem after something has gone measurably wrong and the organization needs the real cause chain rather than a guess. Post-mortems are also called incident reviews or after-action reviews.

Typical triggers:

  • A production outage or security incident
  • A launch that missed its core adoption or revenue target
  • A product or startup shutdown
  • A quarter where key metrics missed by a wide margin

Both share one critical mechanic — and one blind spot

Both rituals rely on the same cognitive move: making failure concrete rather than abstract. Asking a planning room "what could go wrong?" invites hedged, polite answers ("we might slip a week"). Telling the room "it failed; write down why" shifts the mind from defending the plan to constructing plausible causes.

That fluency has a catch documented in The 30% Gap: Mitchell, Russo, and Pennington (1989) showed that prospective hindsight increased the number of failure reasons participants generated by roughly 30%, without testing whether those reasons were accurate. A pre-mortem generates more story-shaped risks; only reality tests which risks mattered.

The Paired-Loop Calibration Test

Running a pre-mortem and a post-mortem on the same initiative turns them from two isolated meetings into a calibration loop. When the post-mortem ends, score every verified root cause against the original pre-mortem list into three buckets:

  1. Predicted & mitigated — surfaced in the pre-mortem and prevented or contained.
  2. Predicted & ignored — surfaced in the pre-mortem, left unowned, and materialized anyway (an execution or authority gap).
  3. Unpredicted or Day-One blind spot — missing from the pre-mortem entirely, showing what kind of risk your team fails to imagine.

A concrete test of bucket 3 appears in our replay of Cydoc's seven-year startup postmortem. When founder Rachel Draelos published nine causes behind her health AI startup's shutdown in February 2026, six were classic story-shaped risks a day-one pre-mortem easily generates (skipping early customer discovery, no dedicated sales owner, workflow friction), two were genuinely unforecastable, and the fatal ninth cause — pricing at run cost ($30/month margin against a $4,000–$6,000 integration cost) — was arithmetic already false on day one. Pairing the pre-mortem against the post-mortem reveals that brainstorming misses non-narrative financial ratios unless you check them separately first.

Common failure mode (in both)

The failure mode is identical in both rooms: the project owner refuses to engage with the conclusions. In a pre-mortem, the owner argues away every imagined failure ("that won't happen here"). In a post-mortem, the owner deflects blame onto external events or individuals.

Both reactions signal low psychological safety. Keep pre-mortem writing silent before group readout, and keep post-mortems strictly blameless so contributors share the full context.

Which should you run first?

If you are starting a significant initiative today, run a 45–60 minute pre-mortem before committing resources, save the ranked risk list with named owners, and commit to grading that list in a post-mortem once the outcome lands.

For the post-mortem root-cause phase, start with the 5 Whys template when the failure looks like a single causal chain, or Fishbone (Ishikawa) when multiple independent factors contributed.

Want both rituals on your phone? Framework for iPhone & iPad includes pre-mortem and structured root-cause templates you can run before launch or after an incident. Free to start.

Sources

  1. Gary Klein — "Performing a Project Premortem," Harvard Business Review (September 2007)
  2. Google SRE Book — "Postmortem Culture: Learning from Failure"
  3. Rachel Draelos — "Why I Shut Down My Bootstrapped Health AI Startup After 7 Years: A Founder's Postmortem" (Glass Box Medicine, 21 February 2026)

Frequently asked questions

What is the difference between a pre-mortem and a post-mortem?

Timing and evidence. A pre-mortem runs before work ships, asks the team to imagine the project has already failed, and produces risk mitigations for the active plan. A post-mortem runs after an outage, launch miss, or shutdown, reconstructs verified causes from logs and timelines, and produces process or architecture changes for the next project.

What is the opposite of a post-mortem?

A pre-mortem is the operational opposite of a post-mortem. While a post-mortem examines a real failure after the fact to extract lessons, a pre-mortem runs before launch and treats a hypothetical future failure as if it already happened so the team can prevent it.

How does a post-mortem differ from a retrospective?

A retrospective runs on a fixed cadence (such as every two-week sprint) whether anything broke or not, focusing on team workflow and collaboration. A post-mortem is event-triggered after a significant failure or incident and focuses on timeline reconstruction, root cause, and prevention.

Should post-mortems be blameless?

Yes — blameless post-mortems are standard practice in engineering and operations, including Google's SRE culture. When naming individuals carries punishment, people withhold context and systemic root causes stay hidden. Blameless means examining the system and incentives that made the mistake possible rather than blaming the operator.

When do you not need a pre-mortem?

Skip a pre-mortem for low-stakes, easily reversible decisions where the cost of being wrong is small. Reserve the 45–90 minute session for launches, migrations, pricing changes, or strategic bets that are expensive to undo.

More comparisons

All comparisons →