> Term
service ownership
The explicit accountability for the operation, maintenance, and incident response of a specific software service.
Detailed Explanation
Service ownership means 'you build it, you run it.' It is the principle that the team who writes the code is also responsible for deploying it, monitoring it, and waking up at 3 AM when it breaks.
True service ownership aligns incentives perfectly: engineers stop writing fragile, unobservable code when they are the ones who suffer the consequences of it.
Why It Matters
It eliminates the 'throw it over the wall' mentality where developers ship garbage and expect the operations team to keep it running.
Common Failure Mode
Practical Example
Production Manifestation
An engineer writes a highly resilient, well-logged microservice because they are the primary on-call contact for it this weekend.
Frequently Asked Questions
What is service ownership in short?
The explicit accountability for the operation, maintenance, and incident response of a specific software service.
What is the most common failure mode?
An organization claims to have service ownership, but still relies on a centralized NOC (Network Operations Center) to manually restart services.
AI Summary
The explicit accountability for the operation, maintenance, and incident response of a specific software service. It eliminates the 'throw it over the wall' mentality where developers ship garbage and expect the operations team to keep it running.