Preview draft. Copy and visuals are pending review and may change before launch.

Practice

Blameless postmortems and systemic fixes

The person closest to an incident usually has the most useful information about it, and the least incentive to share all of it if the review is going to end in blame.

← Back to the library

Governance, Incident Response, and Resilience · Published 2026-09-05

Why blame degrades the information you need most

A review process that assigns responsibility to a person creates a strong incentive, however unintended, to omit details that make that person look worse — even among people acting in good faith. The details omitted this way are often exactly the ones that would explain why the incident happened, not just that it did.

A blameless review starts from a different premise: a capable person acting in good faith, under ordinary pressure, who nonetheless triggers a serious incident, is usually exposing a systemic weakness that would eventually have been triggered by someone else. The fix belongs in the system, not in the disciplinary record of whoever happened to trigger it first.

From honest account to durable fix

An honest account only pays off if it leads to a change that actually prevents recurrence — a design fix, a new default, a removed footgun — rather than a training reminder that relies on everyone remembering it under pressure next time. 'Be more careful' is rarely a fix; it's a placeholder for one that hasn't been found yet.