liveBook · Manning

Blameless postmortem

As explained in Build High Value Software Systems

A blameless retrospective is a structured review of an incident that focuses on system conditions and improvements rather than individual fault.

A blameless retrospective reviews a production incident to improve the system rather than assign individual fault. It turns the failure into a question about earlier detection and automatic prevention. section 1.2.3 section 1.2.4

A practical review can turn learning into follow-through:

  • After an incident, ask what could have caught the problem earlier and how to make that check automatic. section 1.2.3 section 1.2.4
  • Record prevention work in a lightweight template, then track it alongside feature work. section 1.2.3

From rollback to an automatic check

A performance problem during the notification-preferences rollout led to automated load tests for database changes. The tests run before staging and flag slow queries or locks, making the prevention work a system check rather than relying on individual vigilance. section 1.2.3

How Build High Value Software Systems covers it

How deep it goes
Defines a recurring retrospective question and lightweight prevention template, but gives no detailed meeting procedure.
Examples
Grounds the practice in a notification-preferences rollback that prompted automated load testing for database changes.
What you can do after
Apply it by asking what could have caught the problem earlier and how to make that check automatic.
How it connects
Connects incident learning with production incidents, automated checks, load testing, and backlog follow-through.

Also explained in

Compare how 2 books explain blameless postmortem →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.