How to Build a Healthy On-call Culture
summary
Shows concrete wins and failures: an Elasticsearch incident that required disabling a cluster and a 2:00 a.m. data fix, survey data linking on-call to cortisol and disrupted mood, and a 57% claim of fewer outages after CI/CD adoption. Describes tooling and workflows actually used — Opsgenie for paging and escalations, Confluence for playbooks — and practices that are deployed and measured: developers-on-call rotations, shadowing, game days, blameless culture, and paid or compensatory time off.
AI-written summary · about
chapters (6)
- 0:00Start
- 6:27Developers on call
- 11:56Heroism is not sustainable Even Iron Man needs backup
- 20:32Sharing knowledge makes everyone smarter
- 22:12Practice boosts confidence
- 24:34KEY TAKEAWAYS
related talks
28mBuilding a healthy on-call culture
30mOn call does not have to suck
44mYou build it, you run it
06mIgnite: Key Factors for Successful 24×7 On-Call Duty
19mIts Time We Rethink On-Call Culture
19mOn-call revolution: Fostering ownership and collaboration
26mBuild a data-driven on-call workflow for your team with atomic habits
27mYou Should Be On Call, too