Course contentsShow
← System Design
Lesson 1350 of 1,91933. Reliability Engineering FoundationsFree lesson

What is a Postmortem?

Blameless analysis after incidents documenting what happened, why, impact, and actions to prevent recurrence.

What is a Postmortem?

You'll learn: What a postmortem is and how it transforms incidents into learning opportunities without assigning blame.

The Core Idea

A postmortem (also called a post-incident review) is a structured, blameless analysis conducted after a significant incident. Instead of asking "Who caused this?" it asks "What happened, why did it happen, what was the impact, and how do we prevent it from happening again?"

Think of it like an airplane crash investigation: investigators examine the black box, interview pilots, and analyze conditions—not to punish anyone, but to make flying safer for everyone. Similarly, postmortems examine system failures to improve reliability.

What a Good Postmortem Includes

A comprehensive postmortem documents:

  • Timeline: Detailed sequence of events from detection to resolution
  • Root Cause Analysis: The underlying system or process failures (often multiple contributing factors)
  • Impact Assessment: Duration of outage, users affected, revenue lost, SLO/error budget burn
  • What Went Well: Effective responses and mitigations during the incident
  • Action Items: Concrete, assigned follow-ups to prevent recurrence
  • Lessons Learned: Broader insights about your system's behavior

The Blameless Philosophy

The "blameless" aspect is crucial. When engineers fear punishment, they hide problems. When they trust the process, they share honest details that reveal systemic issues. You blame broken processes and tooling, not people.

This connects directly to the Blameless Culture principle you learned earlier—postmortems are where that culture manifests in practice.

Why Postmortems Matter

Without postmortems, you repeat mistakes. With them, each incident becomes an investment in resilience. They also help reduce toil by identifying automation opportunities and inform your Error Budget Policies by revealing where to invest engineering effort.

Key Takeaway: A postmortem is a blameless, structured document that transforms incidents into actionable improvements by analyzing what happened, why, its impact, and prevention strategies—turning failure into a learning asset.