Interactive graph
Blameless After-Action Review
Table of Contents
After rollback restores service, the team learns what broke in the system - not who to punish for pushing deploy.
Key Concept
- Rollback Principle gets users back on the old build; blameless after-action review gets judgment back.
- Level 1: Like when the team fixes the broken goal net first - then they talk about what went wrong without picking one kid to blame.
- Level 2: Rollback puts users back on the old build; blameless review puts judgment back - trace what broke in the system after calm returns.
- Level 3: Blameless after-action review pairs with Rollback Principle - fix the runbook after revert, not the person who pushed deploy.
- Level 4: Monday debrief traces the missing env var check, not which intern merged - someone still says “my call” in standup while the room fixes the process.
- Level 5: Same shape as Incident Investigation but culture rule is no punishment theater - Own the Error means naming your call without the room fixing the person instead of the runbook.
- Same shape as Incident Investigation - trace system causes - but the culture rule is no scalpel hunts for a fall guy.
- Own the Error still means someone says “my call” in standup; the room fixes the runbook, not the person.
- Fix the runbook after rollback - not the person who pushed deploy.
Examples
- Bad Friday deploy reverted by lunch - Monday after-action review traced the missing env var check, not which intern merged.
- After the equipment cart tipped twice we changed storage layout - debrief named the hazard, not “trainer was clumsy.”
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| alternative | Rollback Principle | Rollback first; after-action review after calm - not root-cause while users are down |
| contradicts | Normalization of Deviance | when “nobody died” ends the conversation without an after-action review |
| extends | Convert Pain Into Learning | After-action review is the scheduled convert step after harm |
| extends | Failure as Feedback | Miss becomes signal when nobody's hiding to keep their job |
| extends | Incident Investigation | Blameless tone keeps investigation on system causes |
| extends | Learning Organizations | “What broke” line stays until fixed or accepted |
| extends | Measure Then Iterate | After calm, learn what broke with something you would track next time |
| extends | Own the Error | Leader names the miss; room fixes the process, not the person |
