Notesfoundations🌱 seedling
Blameless Postmortem
Also: Postmortem · Post-Incident Review · Incident Retrospective · Just Culture
A blameless postmortem is a written review of an incident that looks for contributing causes in systems and processes rather than individuals, and produces tracked action items. It asks "how did the system allow this?", not "who did it?"
Why it exists
If people are punished for mistakes, they stop explaining them, and the organization loses the information needed to prevent the next one. You can't fix people, but you can fix systems and processes so they support good decisions.
How it works
- Triggers defined in advance: user-visible impact beyond a threshold, any data loss, on-call intervention (rollback, rerouting), slow resolution, monitoring failure.
- Contents: impact, timeline, actions taken, contributing causes, follow-up items with owners.
- Assume good intent: people acted reasonably on the information and tools they had.
- Review and share: senior review for depth of analysis; publish widely so others learn.
Trade-offs
| Gains | Costs |
|---|---|
| honest accounts, systemic fixes | time to write, review and follow through |
| learning spreads across teams | can feel unaccountable if action items aren't tracked |
In practice
- AWS S3 (Feb 2017): a mistyped playbook command removed too many servers. The fix was in the tool: remove capacity more slowly, refuse to go below any subsystem's minimum.
Pitfalls
- "Blameless" with no action items: a write-up nobody reviews might as well not exist.
- Stopping at "human error" as the root cause; it's where the investigation should start.
Connections
- Part of
- Operability
- Related
- Human ErrorChaos Engineering
Recall
These cards are also in your review deck, scheduled with spaced repetition.