Build a data-driven on-call workflow for your team with atomic habits
summary
Claims a repeatable, data-driven on-call workflow inspired by Atomic Habits that cuts alert noise and creates time for improvement, backed by real metrics: an extreme example of 150 pages per day, team scale of 60 billion requests per day at three nines availability, and earlier averages like five pages/day and 15‑minute MTTR. Implements regular charts and reviews driven by Python scripts, a prioritized on-call backlog and an on-duty role that pairs week-long primary shifts with focused remediation.
AI-written summary · about
chapters (10)
- 0:00On-call challenges and data
- 3:52Effective on-call workflow
- 7:06Edge team at Adobe
- 10:18On-call worsened in pandemic
- 12:24Bad habits in team
- 17:17Atomic Habits for solutions
- 19:04Improvements obvious with data
- 21:55Improvements easy and attractive
- 23:20Results and reflections
- 24:47Final thoughts and next steps
related talks
24mWait for Us! Evolving On-Call as Your Company Grows
16mHuman Centered On Call Practices
31mHow to Build a Healthy On-call Culture
30mOn call does not have to suck
19mOn-call revolution: Fostering ownership and collaboration
44mYou build it, you run it
23mFirefighting: The Engineer's Guide to On-Call
50mYou build it, you run it (why developers should also be on call)