InfoQVanessa Huerta Granda32 min readtalkintermediate
Presentation: When Incidents Refuse to End
Summary
This presentation explains how marathon incidents expose the gap between work as imagined and work as done, revealing system interdependencies, organizational fragility, and human limits. Effective response requires structured endurance, humane rotations, and holistic cross-functional coordination, offering significant technical and organizational learning.
- Long-running incidents amplify pressures: time, coordination, cognitive, and visibility on responders.
- Incident Commanders often "parent" responders, ensuring basic needs (food, breaks) are met for effective troubleshooting.
- These incidents are crucial for learning actual system architecture, data flow, and organizational ownership, beyond diagrams.
- "Degradation" (the "D word") is hard to quantify but signifies bad vibes and often leads to prolonged, unclear incidents.
Engineers and engineering leaders can learn how to better prepare for and manage complex, prolonged outages, improving both system resilience and team well-being.
7/10
