Protocol
Mine postmortems for repeated failure patterns
One postmortem explains an event. A set of postmortems can reveal a system.
Before you use it
- Use when
- Individual incidents are being closed but similar failure modes keep returning under different names.
Keep this limit in mind
- Do not copy another organization's incident frequencies as your baseline or force every event into a convenient category.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Periodically classify incidents by trigger, contributing conditions and affected system patterns using a small local taxonomy. Look for concentrations that justify a shared fix: deployment checks, interface design, capacity controls, observability or ownership. Keep the raw incidents visible so the categories do not become a substitute for reading the evidence.
Steps
- Choose a small set of locally meaningful trigger and contributing-factor categories.
- Classify a bounded period of postmortems consistently.
- Identify repeated patterns with enough examples to inspect.
- Create one systemic improvement hypothesis and test whether future incident data changes.
An example
Several unrelated outages may trace back to unsafe configuration rollout rather than three separate 'human errors.'
Check your result
The analysis produces a cross-incident improvement target supported by identifiable incident records.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingMine postmortems for repeated failure patterns
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Use before this ideaMitigate first when the incident is still hurtingUse before this idea
Give every postmortem action a verifiable finish
Evidence and sources
Google SRE uses consistent trigger and root-cause categories across postmortems to perform trend analysis and target systemic improvements.
Categories must fit the local system; Google's historical frequencies should not be copied as expected proportions elsewhere.
Results of Postmortem Analysis · Results of Postmortem Analysis
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.