This standard ensures each platform capability defines clear boundaries of responsibility—what it owns, how it’s used, and where teams maintain control. It streamlines collaboration and fosters autonomy.
Aligned to our "Empower Teams to Self-Serve" policy, this standard avoids confusion, reduces misaligned dependencies, and accelerates delivery. Without it, overlaps and gaps in accountability slow progress and create unnecessary friction.
| Category | Description |
|---|---|
| People & Culture | Platform teams are reactive and siloed. Consumers are uncertain who to ask or what is owned. |
| Process & Governance | No ownership boundaries exist. Support and expectations vary widely between capabilities. |
| Technology & Tools | Interfaces and contracts are undocumented or unclear. Adoption relies on trial and error. |
| Measurement & Metrics | No measurement of adoption friction or ownership confusion. |
| Category | Description |
|---|---|
| People & Culture | Platform teams begin describing scope in conversations. Boundaries are inconsistently understood across teams. |
| Process & Governance | Some capabilities have partial documentation or “how to” guides. Support is reliant on known individuals. |
| Technology & Tools | Usage is informally guided by examples or Slack messages. Platform catalogue is emerging but incomplete. |
| Measurement & Metrics | Support requests begin to be tracked manually. Patterns of friction or confusion are visible but not analysed. |
| Category | Description |
|---|---|
| People & Culture | Platform and product teams co-create and share responsibility boundaries. Ownership is clearly defined and understood. |
| Process & Governance | Capabilities come with published documentation, support expectations, and onboarding guidance. Teams can self-serve confidently. |
| Technology & Tools | A platform catalogue or portal clearly describes each capability, its APIs, and team responsibilities. |
| Measurement & Metrics | Platform usage, support requests, and onboarding feedback are measured to refine boundaries. |
| Category | Description |
|---|---|
| People & Culture | Boundary feedback is part of platform retrospectives. Teams use telemetry to surface gaps in understanding or support. |
| Process & Governance | Boundaries are reviewed regularly with consumers and evolve through iteration. Platform roadmaps reflect consumer pain points. |
| Technology & Tools | API documentation, SLAs, and service maturity indicators are visible and versioned. Self-service usage patterns are tracked. |
| Measurement & Metrics | Platform discoverability, time-to-onboard, and volume of support escalations are tracked and improved. |
| Category | Description |
|---|---|
| People & Culture | Platform teams behave as product teams. Consumers are treated as users whose feedback drives platform evolution. |
| Process & Governance | Responsibility boundaries adapt dynamically to support evolving team needs. Clear feedback loops reinforce continuous improvement. |
| Technology & Tools | Context-aware service documentation and intelligent onboarding guidance are embedded into developer tools. |
| Measurement & Metrics | Metrics drive prioritisation and investment in capability clarity. Gaps in responsibility are proactively resolved before becoming friction. |