The magic of crisis
summary
Claims crisis is a rare window to force technical change: if three of five symptoms appear (fundamental surprise, broken core function, high visibility, perception breakdown, rigid timing), fast work can be approved. Example: a global config push crashes systems; an ad‑hoc automatic shut off script (small shell tool, VM, service account, a unit test) is hardened and deployed in days, stops the outage, and becomes a production resilience measure that prevents several global outages per year.
AI-written summary · about
chapters (7)
- 0:00Crisis engineering intro
- 1:33Global config dangers
- 4:02Useful crisis symptoms
- 12:16Outage scenario analysis
- 15:03Crisis as change chance
- 19:40What is not a crisis
- 21:49Conclusion
related talks
15mIncident Ready: Chaos Engineer Your Incident Response
06mIgnite - Crisis Communication Breakdown
41mLessons from Mission-Critical Systems in Fast-Moving Industries
39mOops!… We F*ed It Up Again: The Art of Staying Calm When Systems Crash
30mIncident Groundhog Day
16mResilient by Design: Architectures for Crisis Response & Recovery
19mManaging Fires: Leadership Through Crisis
44mDeveloping a Culture of Reliability and Resilience through Chaos