governance · version 2026.1
Cloud Governance Forum Map
A governance cadence showing how portfolio, architecture, risk, service and operational forums exchange decisions and evidence.
Accessible diagram transcript
Objects
- Cloud portfolio council: Investment and direction (Governance)
- Architecture review: Patterns and exceptions (Authorities)
- Risk & control forum: Risk acceptance (Authorities)
- Service portfolio forum: Lifecycle decisions (Service ownership)
- Operational review: Performance and actions (Operations)
- Platform delivery teams: Prepare proposals and evidence (Engineering)
Directed relationships
- steerco → architecture: decision envelope (authority)
- steerco → risk: risk appetite (authority)
- steerco → service: portfolio priorities (handoff)
- steerco → operations: performance mandate (handoff)
- delivery → architecture: design proposal (handoff)
- delivery → risk: control evidence (handoff)
- delivery → service: release readiness (handoff)
- operations → delivery: improvement actions (feedback)
When to use it
Use to reduce duplicate committees and clarify which forum owns each class of decision.
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
6 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.