Ownership¶
Teams own their work end to end — delivery, quality, reliability, and support.
Ownership does not stop at deployment.
Every critical system should have a named owner, defined support responsibilities, and clear escalation paths.
What Good Looks Like¶
- Teams support what they build
- Clear ownership exists for every service
- Operational accountability is understood
- Knowledge is documented, not trapped in individuals
Anti-Patterns¶
- Throwing work over organisational boundaries
- Lack of accountability post-deployment
- Key-person dependency for operational knowledge
- Systems with no named owner
Key Questions¶
- Who owns this system?
- What happens when something fails?
- What would happen if a key person left tomorrow?