Service-level objectives and error budgets
Define an explicit reliability target, and treat the tolerable shortfall against it (the error budget) as a resource to spend that gates risk-taking. With budget available, ship; with the budget exhausted, stabilise. The argument between reliability and velocity becomes a shared rule agreed in advance.
Evidence grade: practice A widely adopted practitioner model with clear provenance.
Use it when
Ship-or-stabilise conflicts that keep coming back; making "reliability first" operational instead of decorative.
Where it stops working
It is only as good as leadership's willingness to obey it when that is inconvenient. Shipping through an exhausted budget in front of the organisation shows everyone what the real policy is.
Where the standard uses it
- DE-3Reliability, incident response, and operational ownershipOn-call, SLOs, postmortems, learning from failure.
- CC-5Values, integrity, and ethical judgment under pressureWhat you do when the right call is the costly one.
Sources
- Betsy Beyer, Chris Jones, Jennifer Petoff and Niall Richard Murphy (editors). Site Reliability Engineering: How Google Runs Production Systems. O'Reilly Media, 2016. In the bibliography
Used alongside it
- Artifacts, espoused values, and assumptions practice
- Blameless postmortems practice
- Culture as what is rewarded, tolerated, and punished practice
- DORA stability metrics research
- Incident command practice
- Leading change practice
Cite this model
Chicago, BibTeX and licence →Engineering Management Academy. (2026). Service-level objectives and error budgets. In Engineering Management Academy Body of Knowledge (Version 3.1, TEC.service-level-objectives-and-error-budgets). https://www.engineeringmanagement.academy/body-of-knowledge/techniques/service-level-objectives-and-error-budgets