Postmortem
In one line
A postmortem is a blameless retrospective after an incident — documents root cause, impact, and action items to prevent recurrence.
In simple words
A postmortem is a written analysis created after an incident is resolved. It is blameless — the goal is to understand what happened and improve the system, not to find someone to blame.
A good postmortem includes: summary, impact, timeline, root cause, contributing factors, what went well, what went poorly, action items. The blameless principle: assume everyone did their best. Action items must be tracked to completion.
Example
# Postmortem: API Outage 2024-01-15
## Root Cause: DB connection pool exhaustion after v2.3 deploy
## Impact: 12 min outage, 15% of requests, ~$4,500 lost
## Timeline: 14:03 alert → 14:08 root cause → 14:10 rollback → 14:12 resolved
## Action Items:
- [ ] Add connection pool leak test to CI
- [ ] Alert on pool utilization > 80%The postmortem is blameless — focuses on technical root cause and system improvements. Action items are tracked to completion to prevent recurrence.
Common confusions
Confused with: Root Cause Analysis
The difference: RCA is the technical investigation to find what caused the incident. A postmortem is the complete document including RCA plus timeline, impact, action items. RCA is one section of a postmortem.
Related terms
Related Resources
Related Lessons
- Incident Management
Postmortems.
Decode error messages
Plain-English explanations of common errors — what they mean, why they happen, and how to fix them.