Principled Identification of "Root Causes" Using Techniques...
summary
Argues that reliable root causes are system vs environment vulnerabilities, not upstream triggers; applies safety engineering tools to classify controllable parts, trace the mechanical path from trigger to failure, and prioritize fixes that remove vulnerabilities rather than chasing alerts. Uses a worked bar example: a vent-button band‑aid, an automatic button robot that adds complexity, and a longer fix of redesigning the overheating heater or adding evacuation redundancy. Critiques five whys and recommends near‑miss analysis to reveal latent failures.
AI-written summary · about
chapters (7)
- 0:00The trap of simple fixes
- 2:07Five whys and its flaws
- 4:46Trigger whack-a-mole
- 7:31System vs environment
- 11:35Redefining root cause
- 13:26Designing for resiliency
- 17:10Expanding the scope
related talks
05mIgnite: Root Cause Analysis Fact and Fiction
30mThere is No Root Cause...
40mBuilding Resilience: How to Learn More from Incidents
29mLearning from incidents: how things went right
37mIncidents are a new normal
58mIt's not always application's fault!
31mGetting Good At System Failure Analysis
18mThe System Boundary...