Full Service Ownership & The Lifecycle of a Service
summary
Advocates full service ownership with the concrete rule you build it, you ship it, you own it and shows measurable wins: reduced MTA and MTR via first‑responder subject‑matter experts, runbooks, SLIs/SLOs, and observability tied to on‑call rotations (10–12 people typical, incident commanders rotating every two days). Recommends service tiering (tier 1–3), semantic versioning for APIs, staged deprecation with migration paths, and practice runs called failure Fridays to validate incident response in production.
AI-written summary · about
chapters (8)
- 0:00Introduction and welcome
- 1:09What is full service ownership
- 7:11Defining a service
- 13:32Key functions in service ownership
- 19:34Setting service availability expectations
- 26:14Lifecycle of a service
- 31:28Best practices for adoption
- 38:48Q&A on on-call culture
related talks
24mThe Lifecycle of A Service
38mBuilding Service Ownership Using Documentation, Telemetry, and a Chance to Make
44mYou build it, you run it
26mSustaining Engineering - life after devops?
05mPagerDuty DevOps Service Ownership
26mService Ownership: DevOps for Salesforce
30mService Ownership @Slack
11mOrganizational Chaos & recipes for Service Ownership