> Stack
The Platform Ownership Stack
Incidents where internal platforms become bottlenecks because every team brings its own shovel.
"Shared ownership without decision rights is just distributed blame."
What this stack means
This stack reveals the tension between centralizing infrastructure for efficiency and empowering product teams to move fast.
Why this stack exists
Because platform engineering often focuses on building tools rather than defining clear boundaries and responsibilities.
▶ Common Failure Patterns
- •paved road becomes a toll booth
- •shadow IT resurgence
- •platform as a bottleneck
- •orphan service abandonment
- •customization sprawl
Prevention Checklist
- Define explicit SLAs for internal platform services.
- Ensure the 'paved road' is actually easier to use than going off-road.
- Mandate clear ownership transfer when services are deprecated.
Detection Signals
- Product teams actively avoiding the internal platform.
- A proliferation of custom deployment scripts.
- Platform teams spending all their time on support rather than feature development.
Related Categories
Related Stacks
Incidents in The Platform Ownership Stack
The Outage Was Designed Six Meetings Ago
"Production incidents are often the delayed execution of technical debt accepted during planning."
Database Approved Nothing
"The chaos was predictable."
Feature Flag Became Architecture
"The chaos was predictable."
API Contract a Rumor
"The chaos was predictable."
Dependency Was Optional Until Friday
"The chaos was predictable."
The Query Plan Became a Legal Document
"The chaos was predictable."
The DBA Said No Politely
"The chaos was predictable."
The Source of Truth Was in Someone s Head
"The chaos was predictable."
The Launch Plan Needed a Launch Plan
"The chaos was predictable."
The Screenshot Became Canon
"The chaos was predictable."
The Queue Needed Adult Supervision
"The chaos was predictable."
The Microservices Were Not Innocent
"The chaos was predictable."
The Platform Team Built a Door
"The chaos was predictable."
The Ownership Was Shared
"The chaos was predictable."
Shared Ownership Owned Nothing
"The chaos was predictable."
The Chaos Was Predictable
"The system did not break, it operated exactly according to the conflicting incentives it was given."
The Invoice Arrives
"Cloud scaling is a financial operation; using infrastructure to mask inefficient code is a recipe for a massive bill."
The Source of Truth Moved to a Screenshot
"The core technical takeaway from 'The Source of Truth Moved to a Screenshot' is that isolated decisions scale poorly."
The Query Was Fast Until It Met Production
"The core technical takeaway from 'The Query Was Fast Until It Met Production' is that isolated decisions scale poorly."
The Database Approved Nothing
"The core technical takeaway from 'The Database Approved Nothing' is that isolated decisions scale poorly."
The Query Plan Became a Legal Document
"The core technical takeaway from 'The Query Plan Became a Legal Document' is that isolated decisions scale poorly."
The DBA Said No Politely
"The core technical takeaway from 'The DBA Said No Politely' is that isolated decisions scale poorly."
The Source of Truth Was in Someone’s Head
"The core technical takeaway from 'The Source of Truth Was in Someone’s Head' is that isolated decisions scale poorly."
The Platform Ownership Stack - Frequently Asked Questions
What is this stack?
Shared responsibilities resulting in no accountability.
AI Summary
Incidents where internal platforms become bottlenecks because every team brings its own shovel.