liveBook · Manning

Postincident analysis

As explained in Build High Value Software Systems

A post-incident review is a structured examination of an operational incident and the conditions that allowed it to occur.

Post-incident analysis examines the systemic conditions that allowed an operational failure, rather than asking who caused it. Treat each incident as a chance to change the system, not just document what happened. section 12.6.1

A review should lead to a concrete improvement, such as:

  • Adding a pipeline constraint to prevent a mistake. section 12.6.1
  • Updating an executable runbook for incident response. section 12.6.1
  • Improving an alert and defining the response it should trigger. section 12.6.1

Turn a diagnosis delay into a measured change

If diagnosis takes 22 minutes because an alert points to a symptom, a kaizen card can assign an owner to add causal context to the five most-used alerts, targeting diagnosis under 10 minutes within four weeks. section 12.6.1

Reviews can also expose operational waste that dashboards miss, such as time spent searching for an outdated runbook or comparing environments. Blameless discussion and visible follow-through help make it safe to raise these problems. section 12.6.1 section 13.2

Figure 13.3 The reinforcing loop between honesty, action, and trust.

The figure shows how honesty, action, and trust reinforce one another in a review culture. section 13.2

How Build High Value Software Systems covers it

How deep it goes
Defines a systemic, non-blaming focus and concrete improvement outputs, but does not lay out a full review procedure.
Examples
Uses wasted time searching for runbooks and a kaizen card for improving alerts as examples.
What you can do after
Apply it via a kaizen card that assigns an owner, specifies a change, and sets a measurable target.
How it connects
Links reviews to kaizen, standard work, andon, poka-yoke, and psychological safety.

Also explained in

Compare how 3 books explain postincident analysis →

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.