On-call revolution: Fostering ownership and collaboration
summary
Consolidating four team rotations into one shared on-call pool (nine people) cuts on-call cost by about 75% cost reduction, reduces noisy alerts by up to 80% fewer after-hours alerts, and raises engagement by ~5% then 3%, using Patient Duty, Slack, Confluence, a Python script to generate weekly incident summaries, ticketing and simple runbooks, plus postmortems and weekly catchups — the rotation, tooling and processes are built and demonstrably improve reliability and ownership.
AI-written summary · about
chapters (12)
- 0:00Introduction and context
- 2:00The challenge of losing SRE
- 3:37Defining the new strategy
- 5:13Securing buy-in and budget
- 7:00Tools and operational processes
- 8:38Daily on-call experience
- 10:56Cultural shifts and outcomes
- 12:01Business impact and metrics
- 12:44Future with SLAs and SLOs
- 14:13Roadmap for implementation
- 15:12Overcoming common myths
- 17:15Recap and conclusion
related talks
29mCalling out a terrible on call system
16mHuman Centered On Call Practices
31mHow to Build a Healthy On-call Culture
26mBuild a data-driven on-call workflow for your team with atomic habits
30mFixing out-of-hours on-call
19mIts Time We Rethink On-Call Culture
22mRaise a Production System:Making on-call human-scale w/ Observability & Trust
28mA Tale of Two Rotations Building a Humane & Effective On Call