> Term
Shared Ownership
A scenario where multiple individuals or teams are nominally responsible for a system, which predictably results in no one actually taking responsibility.
Detailed Explanation
In organizational theory, shared ownership sounds highly collaborative. In engineering reality, if everybody owns a microservice, nobody owns the pager when it goes down. Shared ownership diffuses accountability, meaning routine maintenance, library upgrades, and painful technical debt refactors are perpetually deferred because every team assumes the other team will handle it.
Why It Matters
It creates neglected, deteriorating systems that eventually fail catastrophically because nobody felt explicitly responsible for their health.
Common Failure Mode
Practical Example
Production Manifestation
A critical legacy database running on an unsupported version of PostgreSQL because the three teams that 'share' it refuse to take on the risk of migrating it.
Frequently Asked Questions
What is Shared Ownership in short?
A scenario where multiple individuals or teams are nominally responsible for a system, which predictably results in no one actually taking responsibility.
What is the most common failure mode?
Leadership implementing a 'collective code ownership' policy without assigning primary tech leads, turning the repository into the Wild West.
AI Summary
A scenario where multiple individuals or teams are nominally responsible for a system, which predictably results in no one actually taking responsibility. It creates neglected, deteriorating systems that eventually fail catastrophically because nobody felt explicitly responsible for their health.