Starting patterns, not prescriptions

Choose a deliberate center of gravity.

An archetype is a starting hypothesis. The work is to make its decision rights, delivery boundaries and known trade-offs explicit.

01

Centralized CCoE

A central team concentrates governance, architecture and enablement to establish consistency and accelerate early maturity.

Strong whenClear enterprise standards · Concentrated expertise
Inspect trade-offs
02

Federated governance

A small central core defines minimum guardrails while capable platform and product teams make bounded local decisions.

Strong whenGreater product autonomy · Decisions closer to delivery
Inspect trade-offs
03

Hub-and-spoke cloud operating model

A central governance and platform hub provides common guardrails and services while domain spokes retain workload outcomes and bounded delivery authority.

Strong whenShared foundations with local context · Explicit enterprise minimums
Inspect trade-offs
04

Platform-product operating model

Reusable cloud capabilities are managed as internal products with named consumers, outcome roadmaps, engineering ownership and measurable service performance.

Strong whenClear consumer and product outcomes · Continuous platform improvement
Inspect trade-offs
05

MSP-led cloud operating model

An external provider executes substantial engineering or operations while a deliberate retained organization owns architecture, service, risk and commercial outcomes.

Strong whenRapid access to operational capability · Clear service-based delivery boundary
Inspect trade-offs