Blameless postmortems: documenting the timeline, causes and actions

Goal

Learn from an incident in a way that changes the system, not just the caution of the people involved, and make the findings available beyond the team.

Prerequisites

The chapter "Postmortem Culture" in the Google SRE book lists common triggers: user-visible downtime or degradation beyond a threshold, data loss of any kind, on-call intervention (rollback, rerouting traffic), a resolution time above a limit, and a monitoring failure. It describes blamelessness as a principle of SRE culture: the document identifies the contributing causes without accusing any person or team of inappropriate behavior. You need the timeline from alerts, logs and chat history, and an author who is not solely the person who was on call.

Steps

1. Check the threshold: does the incident meet one of the agreed triggers? If not, a ticket is enough; postmortems for minor issues devalue the format.
2. Reconstruct the timeline with timestamps, phrased as observations ("alert X at 02:14", "rollback started at 02:31") rather than interpretations.
3. Describe the impact in terms of users and in numbers: which function, how long, how many requests, records or customers.
4. Collect the contributing causes; there are usually several. The guiding question is "What made this possible?", not "Who did this?"; a person who was able to run a command that should not have been possible is a finding about the system.
5. Record what went well, what went badly and where luck played a part. Today's near miss is tomorrow's outage.
6. Write actions that are concrete, assigned to one person and have a deadline: a missing alert, a missing test, a runbook section, a lock in the deploy. Actions that remove the failure mode take priority over those that call for more care.
7. Review the draft with the team, publish it, and track the actions until they are completed.

Expected result

A document from which a new team member can understand the outage and how it was resolved; completed actions; a climate in which near misses are reported.

Limits and test basis

Blameless does not mean without consequences: the actions have owners. A postmortem whose actions are left undone teaches the team that reporting achieves nothing. The structure and triggers follow the cited chapter; no measurement is claimed here of the effect on people's willingness to report.