Blameless postmortems
Incident reviews that ask how the system allowed the failure and what to change (process, tooling, guardrails) instead of who to blame. This is the mechanism that makes honesty about failure safe, and so makes reliability improvable.
Evidence grade: practice A widely adopted practitioner model with clear provenance.
Use it when
After every significant incident or failed launch. It matters most when the stakes are highest and a senior person is involved, because that review is where the culture gets written.
Where it stops working
Blameless does not mean free of consequences. Patterns of recklessness are performance matters and are handled separately. A review whose actions die in a backlog is a ritual and fixes nothing.
Where the standard uses it
- DE-3Reliability, incident response, and operational ownershipOn-call, SLOs, postmortems, learning from failure.
- CC-1Psychological safety and productive conflictSafe to speak, expected to disagree, committed once decided.
Sources
- John Allspaw. Blameless PostMortems and a Just Culture. Etsy, Code as Craft (engineering blog), 2012. In the bibliography
- Betsy Beyer, Chris Jones, Jennifer Petoff and Niall Richard Murphy (editors). Site Reliability Engineering: How Google Runs Production Systems. O'Reilly Media, 2016. In the bibliography
Used alongside it
- Conflict then commitment practice
- DORA stability metrics research
- Incident command practice
- Psychological safety research
- Service-level objectives and error budgets practice
- The five keys of team effectiveness research
Cite this model
Chicago, BibTeX and licence →Engineering Management Academy. (2026). Blameless postmortems. In Engineering Management Academy Body of Knowledge (Version 3.1, TEC.blameless-postmortems). https://www.engineeringmanagement.academy/body-of-knowledge/techniques/blameless-postmortems