liveBook · Manning

Blameless postmortem

A blameless postmortem is a structured incident review that examines contributing conditions and corrective improvements without assigning individual fault.

How 2 Manning books explain it

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.

How it is used
Uses incident reviews to turn production failures into system-level prevention work.
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.

Read how Build High Value Software Systems explains blameless postmortem →

Shipping Go: Develop, deliver, discuss, design, and go again

A blameless postmortem is a structured review of an incident that seeks its root causes and process improvements without assigning personal blame.

How it is used
Uses incident reviews to learn from failures while preserving developers’ ability to contribute and improve delivery.
How deep it goes
Connects review to root causes, alerts, pipeline safeguards, rollback, and metrics, but does not provide a formal meeting checklist.
Examples
Uses failed builds and deployments, email or Slack alerts, rollback, pipeline checks, and metrics for flaky tests and build failures.
What you can do after
Diagnose/debug with a shared postmortem, identify process changes, and improve checks, visibility, recovery, or collaboration.

Read how Shipping Go: Develop, deliver, discuss, design, and go again explains blameless postmortem →

Also covered in

Related concepts

Questions about blameless postmortem

What is blameless postmortem?

A blameless postmortem is a structured incident review that examines contributing conditions and corrective improvements without assigning individual fault.

Which Manning books explain blameless postmortem?

Build High Value Software Systems and Shipping Go: Develop, deliver, discuss, design, and go again.

What is the difference between blameless postmortem and after-action report?

A blameless postmortem is a structured incident review that examines contributing conditions and corrective improvements without assigning individual fault. An after-action report is a structured post-incident or post-project account that documents what happened, relevant facts, lessons learned, and resulting actions.

What is blameless postmortem a kind of?

Blameless postmortem is a kind of postmortem. A postmortem is a retrospective analysis of an event or incident that examines what happened, its causes and effects, and lessons or actions for improvement.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.