consulting tool · version 2026.1

Cloud Infrastructure Capability Map

A capability-oriented view of governance, architecture, platform, service, operations and enabling disciplines.

Cloud Infrastructure Capability Map. A capability-oriented view of governance, architecture, platform, service, operations and enabling disciplines.
PNG preview2400 × 960 px26 KBVersion 2026.1 · reviewed 2026-09-08
Explore semantic layers
Cloud Infrastructure Capability Map previewdirectionguardrailsunit economicscontrolspatternsroadmapreleaseservice levelsfeedbackadoption insightStrategy & portfolio: Direction and investmentStrategy & portfolioDirection and investmentGovernance & policy: Guardrails and decisionsGovernance & policyGuardrails and decisionsFinOps & commercial: Economics and suppliersFinOps & commercialEconomics and suppliersSecurity & assurance: Risk and evidenceSecurity & assuranceRisk and evidenceArchitecture: Patterns and standardsArchitecturePatterns and standardsPlatform product: Roadmap and adoptionPlatform productRoadmap and adoptionPlatform engineering: Automation and productsPlatform engineeringAutomation and productsService management: Catalogue and lifecycleService managementCatalogue and lifecycleCloud operations: Reliability and supportCloud operationsReliability and supportDeveloper enablement: Paved-road adoptionDeveloper enablementPaved-road adoption
Accessible diagram transcript

Objects

  • Strategy & portfolio: Direction and investment (Governance)
  • Governance & policy: Guardrails and decisions (Governance)
  • FinOps & commercial: Economics and suppliers (Governance)
  • Security & assurance: Risk and evidence (Authorities)
  • Architecture: Patterns and standards (Authorities)
  • Platform product: Roadmap and adoption (Service ownership)
  • Platform engineering: Automation and products (Engineering)
  • Service management: Catalogue and lifecycle (Service ownership)
  • Cloud operations: Reliability and support (Operations)
  • Developer enablement: Paved-road adoption (Engineering)

Directed relationships

  • strategygovernance: direction (handoff)
  • governancearchitecture: guardrails (authority)
  • economicsproduct: unit economics (handoff)
  • assuranceengineering: controls (authority)
  • architectureengineering: patterns (authority)
  • productengineering: roadmap (handoff)
  • engineeringservice: release (handoff)
  • serviceoperations: service levels (handoff)
  • operationsproduct: feedback (feedback)
  • enablementproduct: adoption insight (feedback)
01

When to use it

Use to scope an assessment, structure interviews or connect operating-model functions to improvement initiatives.

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