| Architecture through life | Involvement peaks around strategy and design, then reduces after deployment. | Accountability runs from Strategy to Retirement, including operation, optimisation, debt and decommissioning. |
| Operational architecture | After 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 model | EA, 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. |
| Governance | Success means complying with standards and passing a review board. | Assurance asks whether the intended outcome survived delivery and remains true in production. |
| Measurement | Scorecards count reviews, standards, meetings, exceptions and attendance. | ODMs measure what changed because Architecture existed; contributing indicators expose deterioration early. |
| Quality | Review 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. |
| Economics | Value 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 commitments | Architecture 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. |
| Conformance | Conformance is checked at a design gate and then assumed. | Production drift, technology currency and debt are measured after deployment. |
| Scale | More demand is answered mainly by adding architects. | Patterns, guardrails and practitioner uplift make routine design self-service and reserve architects for novel risk. |