operating model · version 2026.1
Cloud Platform Operating Model
A platform-product lifecycle connecting consumers, architecture, engineering, service ownership and operations.
Accessible diagram transcript
Objects
- Product teams: Consume paved roads (Consumers)
- Platform product management: Outcomes and roadmap (Service ownership)
- Cloud Architecture: Patterns and constraints (Authorities)
- Platform Engineering: Build reusable capabilities (Engineering)
- Service Ownership: Catalogue and lifecycle (Service ownership)
- Cloud Operations: Run and improve (Operations)
- Technology providers: Products and support (Providers)
Directed relationships
- consumer → product: needs (handoff)
- product → architecture: priorities (handoff)
- architecture → engineering: direction (authority)
- product → engineering: roadmap (handoff)
- engineering → operations: handover (handoff)
- service → operations: service levels (handoff)
- provider → engineering: capability (handoff)
- operations → product: feedback (feedback)
When to use it
Use to move a platform team from ticket fulfillment toward product ownership.
What to challenge
- Separate accountable authority from delivery execution.
- Make every important handoff directional and reviewable.
- Treat this reference pattern as a starting point, not a prescription.
Adapt it responsibly
- Rename functions to match the organization vocabulary.
- Remove elements that are genuinely out of scope.
- Validate decision rights and handoffs with accountable stakeholders.
Model contents
7 objects and 8 directed relationships. Every object keeps a stable semantic ID.
One model, multiple representations
The browser view and editable file are generated from the same canonical graph, so labels, roles and relationship direction stay aligned.
Clear visual grammar
Shape, color and connector style distinguish actors, governance, authorities, services, engineering, operations and providers.