CEA Practitioner’s Guide — Addendum C

Overview

Addendum C expands Section 4 of the Practitioner’s Guide by providing the structural, organizational, and governance detail required to operate an EA function at enterprise scale. While the main guide introduces the operating model conceptually, this addendum serves as the practical manual for designing the EA organization, defining architect roles, establishing governance, building culture, and demonstrating value.

The addendum covers centralized, federated, and hub‑and‑spoke organization models; detailed role profiles for every architect type; ARB design and operating procedures; Community of Practice structures; EA metrics; tooling strategy; team building; and a multi‑year maturity roadmap.

What’s Inside

• Three EA organization design models (centralized, federated, hub‑and‑spoke)
• Detailed role profiles for all architect types
• Tiered ARB design, membership, and operating procedures
• Architecture Community of Practice programme design
• EA metrics framework for portfolio health, compliance, and business value
• Team building, hiring, and career progression guidance
• EA tooling categories and implementation principles
• EA operating calendar and practice rituals
• Multi‑year maturity roadmap for enterprise‑scale EA practices

Executive Summary

The EA operating model defines how architecture work is organized, governed, and executed across the enterprise. It is the CEA’s most consequential design responsibility — determining how architecture authority flows, how standards are applied, how architects collaborate, and how the practice scales as the organization grows.

This addendum provides the depth required for CEAs to design and operate a scalable, credible, and high‑impact EA function. It explains how to structure the EA organization, define architect roles, establish governance mechanisms, build a community, measure value, and mature the practice year over year.

Together with Addendum A (ADM execution) and Addendum B (deliverables reference), Addendum C completes the operational foundation for enterprise‑scale architecture leadership.