Ignite: Key Factors for Successful 24×7 On-Call Duty
summary
A cautionary on-call case study shows weekly planning in Excel and physical phones lead to noisy ringtones, missed responsibility and sleepless engineers; a handover took two people awake for hours and only a temporary workaround fixed the incident. Recommended stack-level fixes include on-call calendar with automatic escalations and routing by severity, embedded error logs and KB links in alerts, gentle wake via a fitness band workflow, and external heartbeats/website checks to detect internet outages so alerts remain reliable.
AI-written summary · about
related talks
28mBuilding a healthy on-call culture
31mHow to Build a Healthy On-call Culture
19mIts Time We Rethink On-Call Culture
30mOn call does not have to suck
49mAgainst On-Call: A Polemic
06mIgnite | When Email or SMS are not enough
23mFirefighting: The Engineer's Guide to On-Call
05mOn-Call in a World Full of Toil