Skip to content

Postmortem

← All terms · Software culture & jargon

Also called Incident review, retrospective

A blameless review written after an incident to explain what happened, why it happened, and how to prevent it from happening again.

What it is

A postmortem focuses on learning, not blaming. It records the timeline, impact, contributing factors, and action items so the team can improve systems and response habits.

When you would use it

You use a postmortem after a serious incident or repeated failure that deserves careful analysis and follow-through.

Common operations

  • Reviewing outages
  • Capturing lessons learned
  • Tracking follow-up fixes

Related terms

Where this is taught

No learning path uses this term yet. Browse the Learning Atlas for guided sequences through related ideas.