‹

09. The Postmortem — Turning an Outage Into an Asset

EN

09. The Postmortem — Turning an Outage Into an Asset

The Institutional Shift of Blameless Review

The practice of the blameless postmortem emerged as a structural method to pivot from individual blame toward organizational learning by removing the fear of punishment. John Allspaw of Etsy pioneered this approach in his 2012 article "Blameless PostMortems and a Just Culture" to redefine how engineers interact with complex system failures. Google SRE has further institutionalized this methodology within their internal processes, as detailed in their workbook chapter on postmortem culture, to ensure systemic improvement occurs. The primary goal is to treat an outage as an asset for knowledge, rather than a point of failure that requires the termination of personnel. By 2012, this cultural shift began to define the standard for how technology firms process complex incidents without resorting to the destructive cycle of blame.

Measuring the Artifacts of Failure

The Verica Open Incident Database, known as the VOID 2022 report, analyzed nearly 10,000 incident reports from just under 600 companies to understand industry trends. This massive empirical survey, published in 2022, serves as the largest existing dataset regarding how organizations document the boundaries where their complex systems fail. The data revealed that postmortem practice remains wildly inconsistent across the industry, with most public incident reports failing to identify any clear root cause. Near-miss analysis is almost nonexistent in these documents, leaving a significant gap in how companies learn from events that did not result in total collapse. While these artifacts are collected, the VOID report measures the documentation itself rather than whether these reviews actually reduce the rate of future system incidents.

The Gap in Causal Evidence

There is no independent, reliable dataset that allows researchers to confirm whether postmortem learning causally reduces future incident rates, a limitation noted in academic literature. A 2024 ACM workshop paper on postmortem action items explicitly documents that these items routinely go unimplemented, which undercuts the assumption that review produces change. This absence of evidence is not a minor detail but a fundamental ambiguity regarding the efficacy of the postmortem as an institutional tool for reliability.

Example: A postmortem is a map of a territory that has already shifted, which is only useful if the organization actually builds the roads.

Verdict. The postmortem is an essential ritual for internal communication, but its capacity to prevent future failure remains an unproven hypothesis without causal data.

Overturned if: A longitudinal study succeeds in establishing a statistical link between the rigor of specific postmortem action items and a measurable decline in incident frequency.

Sources. 2012 · Allspaw, J., "Blameless PostMortems and a Just Culture" — Etsy Code as Craft · 2022 · Verica / Nash, C., "The VOID Report 2022" — Verica

บทถัดไป · 10 / 1210. Resilience Engineering — Work as Imagined and Work as Done
Size
Page
Font

At The Seams

❦
101. The Seam — Why Failure Concentrates Where Parts Meet202. Units and Assumptions — The Mismatch Nobody Owns303. The Handoff — Where Information Goes to Die404. Protocol Drift — When Two Sides Disagree About the Contract505. Timeouts and Retries — The Cure That Causes the Disease606. The Silent Success — Failure That Reports Everything Is Fine707. Latent Conditions — Accidents That Were Already There808. The Blame Reflex — Why 'Human Error' Ends the Inquiry909. The Postmortem — Turning an Outage Into an Asset1010. Resilience Engineering — Work as Imagined and Work as Done1111. Control, Not Components — Leveson's Reframing1212. Finding Your Own Seams — The Procedure