Architecture / Architecture Operating Models

A practical operating model for architecture

Architecture Operating Models

Connect enterprise direction, solution delivery and operational reality through explicit services, lifecycle accountabilities and evidence-led outcome measures.

3architecture roles
10through-life stages
54catalogue services
16outcome measures

Start here

From mandate to measurable outcomes

An architecture function needs a clear mandate, customer-facing services, defined intervention points across delivery and a measurement system that shows whether architecture changes outcomes.

01 · Roles→02 · Lifecycle→03 · Services→04 · Outcomes→05 · Evidence
01 · Mandate

Roles and SFIA 9

Scope and accountabilities for enterprise, solutions and operational architects.

Open guide →
02 · Intervention

Through-life lifecycle

Leadership, contribution and hand-offs across three architecture layers.

Open guide →
03 · Offer

Service catalogues

The 18 customer-facing services offered by each role.

Open guide →
04 · Accountability

Outcome Delivery Model

Six families, outcome measures, ownership and PLAs.

Open guide →
05 · Evidence

Measurement system

Indicators, sources, transformations, controls and scorecards.

Open guide →
06 · Adoption

Implementation roadmaps

From definition to an institutionalised PLA-grade rhythm.

Open guide →

Why this is different

Architecture as a through-life control and decision capability

This model does not stop at producing designs or governing projects. It joins direction, delivery, live-estate integrity, measurement and investment into one closed loop.

ApproachConventional EA/SA guidanceThis operating model
Architecture through lifeInvolvement peaks around strategy and design, then reduces after deployment.Accountability runs from Strategy to Retirement, including operation, optimisation, debt and decommissioning.
Operational architectureAfter go-live, responsibility transfers to Operations, SRE, platforms or service management.The OA retains architectural ownership of drift, resilience, observability, capacity, lifecycle and operability.
Role modelEA, solution architecture and operations often work as separate organisational domains.EA → SA → OA is one continuous value chain: direction becomes a solution, then remains architecturally coherent in service.
GovernanceSuccess means complying with standards and passing a review board.Assurance asks whether the intended outcome survived delivery and remains true in production.
MeasurementScorecards count reviews, standards, meetings, exceptions and attendance.ODMs measure what changed because Architecture existed; contributing indicators expose deterioration early.
QualityReview completion or design compliance acts as the proxy for quality.Defect containment measures where flaws are discovered and makes escapes into build, test or production visible.
EconomicsValue is expressed qualitatively through alignment, consistency and risk reduction.Rework cost, technical debt and investment outcomes connect performance to capacity and cost trade-offs.
Performance commitmentsArchitecture works to informal expectations or review-turnaround SLAs.Performance Level Agreements make capability level and the investment required to sustain it an explicit business choice.
ConformanceConformance is checked at a design gate and then assumed.Production drift, technology currency and debt are measured after deployment.
ScaleMore demand is answered mainly by adding architects.Patterns, guardrails and practitioner uplift make routine design self-service and reserve architects for novel risk.
Intent→EA→SA→Delivery→OA→Measurement & learning↺

The decisive change happens after deployment

A conventional lifecycle often ends architectural accountability when a project hands over to BAU. Here, the Operational Architect remains accountable for whether the live implementation still represents the intended architecture. Drift, ageing technology, debt, resilience weaknesses and operational workarounds therefore become architecture information—not merely operational problems.

How it fits together

Three roles, one value stream

The Enterprise Architect sets direction across the estate. The Solutions Architect translates direction into buildable change. The Operational Architect makes operability, resilience and lifecycle health explicit. They are separate accountabilities but one system of work.

Follow the value stream

Complete source

Architecture roles, services and ODM workbook

Download the original workbook. Illustrative thresholds and values remain clearly labelled.

Download XLSX