governance · version 2026.1

Cloud Decision Rights Overview

A decision-rights map connecting recurring decision classes to one final accountable authority and their execution owners.

Cloud Decision Rights Overview. A decision-rights map connecting recurring decision classes to one final accountable authority and their execution owners.
PNG preview2400 × 963 px24 KBVersion 2026.1 · reviewed 2026-09-08
Explore semantic layers
Cloud Decision Rights Overview previewaccountableaccountableaccountableaccountableprioritiesconstraintsconditionsacceptancePortfolio priorities: Investment decisionPortfolio prioritiesInvestment decisionTechnical standards: Architecture decisionTechnical standardsArchitecture decisionRisk acceptance: Control decisionRisk acceptanceControl decisionService release: Lifecycle decisionService releaseLifecycle decisionCloud Governance / CCoE: Portfolio authorityCloud Governance / CCoEPortfolio authorityCloud Architecture: Standards authorityCloud ArchitectureStandards authoritySecurity & Risk: Risk authoritySecurity & RiskRisk authorityService owner: Release authorityService ownerRelease authorityPlatform Engineering: Execution ownerPlatform EngineeringExecution ownerCloud Operations: Operational acceptanceCloud OperationsOperational acceptance
Accessible diagram transcript

Objects

  • Portfolio priorities: Investment decision (Service ownership)
  • Technical standards: Architecture decision (Service ownership)
  • Risk acceptance: Control decision (Service ownership)
  • Service release: Lifecycle decision (Service ownership)
  • Cloud Governance / CCoE: Portfolio authority (Governance)
  • Cloud Architecture: Standards authority (Authorities)
  • Security & Risk: Risk authority (Authorities)
  • Service owner: Release authority (Authorities)
  • Platform Engineering: Execution owner (Engineering)
  • Cloud Operations: Operational acceptance (Operations)

Directed relationships

  • portfolioccoe: accountable (accountability)
  • standardsarchitecture: accountable (accountability)
  • risk-decisionsecurity: accountable (accountability)
  • service-decisionowner: accountable (accountability)
  • ccoedelivery: priorities (handoff)
  • architecturedelivery: constraints (authority)
  • securitydelivery: conditions (authority)
  • owneroperations: acceptance (handoff)
01

When to use it

Use to challenge unclear accountability before building a detailed decision register or RACI.

02

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.
03

Adapt it responsibly

  1. Rename functions to match the organization vocabulary.
  2. Remove elements that are genuinely out of scope.
  3. Validate decision rights and handoffs with accountable stakeholders.
04

Model contents

10 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.

Make this model your own.

Rename objects, adjust the scope and download an editable version. Your changes stay in this browser; no account is required.

Customize this diagram