PagerDuty DevOps Service Ownership

on YouTube ↗05m

" summary

PagerDuty applies three Zen rules to service ownership: start where you are, evolve constantly, fail often. Concrete changes include building a reliable index in PagerDuty, renaming services to a clear purpose and tier, assigning each service to a team (not an individual), deleting stale alerts, and updating runbooks. Result: fewer wakeups for unknown owners, faster incident routing, and measurably happier on‑call responders as teams incrementally fix forward.

AI-written summary · about

" chapters (5)

1. 0:00Introduction
2. 0:30Ron Burgundy
3. 1:00Service Ownership
4. 2:00Fix Forward
5. 2:45Accept Impermanence

" related talks

• 48muses PagerDuty to speed up DevOps & cloud innovationMark Huber, Julian Dunn · AWS re:Invent 2019
• 45mHow to Infect your Organization with Humane OpsMatt Stratton · DevOpsDays Salt Lake City 2018
• 44mFull Service Ownership & The Lifecycle of a ServiceDaniel Afonso · DevOpsDays Prague 2025
• 33mFamiliar Smells I’ve Detected in Your Systems Engineering Organization and How to Fix ThemDave Mangot · LISA18
• 53mIndustry leaders share how to automate with PagerDuty and AWSAWS re:Invent 2022
• 16mHuman Centered On Call PracticesNajla Elmachtoub · CascadiaJS 2020
• 30mReliability Engineering for HumansHannah Foxwell · Cloud Foundry Summit North America 2019
• 23mMotivational Leadership Driving Change Through Empowered EngKimberly Schmitt · CTO Craft Con: Berlin 2025