Learning Inside the Box: The Scope of Incident Reviews
summary
Incident reviews focus on concrete scope: start timelines before the declaration, include planning and hallway decisions, and map which systems and orgs actually saw what. Use timestamped logs plus a visualization practice — hierarchical control flow diagrams annotated in red to show safety constraints and a missing coordination link (goals, strategies, decisions, communications). Pre-warm distant teams to avoid defensiveness and use a separate action-item meeting so learning stays front and center.
AI-written summary · about
chapters (8)
- 0:00Incident review scope
- 1:46Building incident timeline
- 5:39System diagrams for clarity
- 8:28Coordination gaps in systems
- 10:18Diverse teams in reviews
- 13:06Accountability versus learning
- 15:38Action items vs sensemaking
- 16:41Conclusion and key takeaways
related talks
37mLearning from Incidents at Scale; Actually Doing Cross-Incident Analysis
37mIncidents are a new normal
13mThe Incident Is The Way: Using Your Incidents to Win...
29mBreak Free of the Template: Incident Writeups They Want to Read
30mHow Did Things Go Right? Learning More from Incidents
34mIncidents are new normal
39mHuman Observability of Incident Response
40mBuilding Resilience: How to Learn More from Incidents