Body of Knowledge · Glossary
Service ownership
Every service has a named owner responsible for its operation, its interface stability, its documentation and its future. A critical service with no owner comes first, because everything about its health depends on somebody being responsible.
Where the standard develops it
- TJ-3Code review and quality standardsIncluding standards for AI-generated code.
- DE-3Reliability, incident response, and operational ownershipOn-call, SLOs, postmortems, learning from failure.
Related terms
- AI governance
- The explicit, proportionate policy for AI-assisted work.
- Aligned autonomy
- Direction, priorities and boundary standards set centrally, with methods left to teams.
- Blameless postmortem
- An incident review that asks how the system allowed the failure and what to change, rather than who to blame.
- Bus factor
- The number of people who could leave before critical knowledge or capability is lost.
- Contract testing
- Automated verification of the agreement between a service and its consumers, which catches a breaking change at the boundary before integration does.
- DORA metrics
- The four research-validated delivery measures (deployment frequency, lead time for changes, change failure rate, time to restore service).
- Error budget
- The tolerable shortfall against a service-level objective, treated as a resource to spend that gates risk-taking.
- Incident command
- A single defined role, assigned before the incident, that owns coordination and communication so that responders can focus on the fix.
Cite this definition
Chicago, BibTeX and licence →Engineering Management Academy. (2026). Service ownership. In Engineering Management Academy Body of Knowledge (Version 3.1, GLO.service-ownership). https://www.engineeringmanagement.academy/body-of-knowledge/glossary/service-ownership