9.2 Establishing an Architecture Capability & Organizational Structure

9.2 Establishing an Architecture Capability & Organizational Structure

For an enterprise to derive sustained strategic value from enterprise architecture, architecture cannot be treated as an isolated, temporary project. It must be established as a permanent, institutionalized Enterprise Architecture Capability—an enduring enterprise practice with dedicated budget, skilled personnel, standardized processes, governance mechanisms, and supporting tools.

Establishing an EA Capability requires careful design of organizational structures, operational processes, skills frameworks, and integration touchpoints across the business and IT delivery ecosystem.

---

The ADM Lifecycle Connection: Preliminary Phase and Phase H

In the TOGAF ADM, establishing and maintaining an architecture capability is explicitly embedded into the core lifecycle iterative loops:

  +-------------------------------------------------------------------------+
  |                           PRELIMINARY PHASE                             |
  |  - Initial EA Capability Setup                                          |
  |  - Define EA Principles, Frameworks & Customizations                   |
  |  - Establish Architecture Board & Governance Controls                   |
  +-------------------------------------------------------------------------+
                                       |
                                       v
  +-------------------------------------------------------------------------+
  |                      ADM PHASES A THROUGH G (EXECUTION)                 |
  |  - Deliver Architecture Visions, Baselines, Targets & Implementations   |
  +-------------------------------------------------------------------------+
                                       |
                                       v
  +-------------------------------------------------------------------------+
  |                   PHASE H: ARCHITECTURE CHANGE MANAGEMENT               |
  |  - Continuous EA Capability Monitoring & Maturity Review                |
  |  - Refresh EA Frameworks, Tools, Skills & Team Structure                |
  +-------------------------------------------------------------------------+

1. The Preliminary Phase: Establishing the Initial Capability

The Preliminary Phase is where the enterprise architecture capability is born. During this phase, enterprise leaders define:

• "Where" the architecture capability will sit within the enterprise organization.
• "Who" will form the EA team and Architecture Board.
• "How" TOGAF will be tailored to fit enterprise culture and processes.
• "What" tools, repositories, and architecture principles will govern delivery.

2. Phase H (Architecture Change Management): Maintaining and Evolving the Capability

An EA Capability is dynamic; as enterprise strategy, business models, and technology landscapes evolve, the EA capability itself must adapt. Phase H ensures that the architecture capability is continuously monitored, assessed for maturity improvements, re-aligned with emerging digital drivers, and refined over time.

---

The Five Core Dimensions of an EA Capability

Building a robust EA Capability requires addressing five interconnected operational dimensions:

---

Organizational Models for Enterprise Architecture Teams

How an EA team is structured within an enterprise profoundly impacts its effectiveness, cultural acceptance, and alignment with business units. TOGAF identifies three primary organizational models:

1. Centralized EA Structure

In a Centralized structure, all architects belong to a single, central Enterprise Architecture group reporting directly to executive leadership (e.g., Chief Architect or CIO).

• Pros: Strong consistency, unified standards, easy alignment across enterprise domains, efficient repository management.
• Cons: Risk of becoming an "Ivory Tower" detached from business unit realities; potential bandwidth bottlenecks during high project volumes.
• Best Suited For: Highly centralized enterprises, single-business corporations, or organizations initiating early-stage EA practices.

2. Decentralized (Embedded) EA Structure

In a Decentralized structure, architects are embedded directly within individual business units, divisions, or regional IT teams, reporting locally.

• Pros: High business domain intimacy, rapid responsiveness to local project needs, strong rapport with local business stakeholders.
• Cons: High risk of architectural fragmentation, duplicated technology investments, conflicting standards, and lack of enterprise-wide cohesion.
• Best Suited For: Highly autonomous conglomerates or holding companies with unrelated business units.

3. Federated EA Structure (Recommended Hybrid)

A Federated structure balances central control with local agility. A core central EA team manages enterprise-wide strategy, principles, standards, and global governance, while domain/divisional architects are embedded within business units to guide local project execution.

• Pros: Combines strong enterprise-wide standards and governance with high local responsiveness and business domain expertise.
• Cons: Requires sophisticated matrix management, clear RACI definitions, and active communication channels between central and divisional architects.
• Best Suited For: Large, complex multi-division enterprises, global corporations, and digital enterprises operating at scale.

---

Operationalizing EA as an Enterprise Practice

To drive business value, the EA Capability must seamlessly integrate with existing enterprise business and operational management practices:

• Integration with Portfolio & Capital Planning: Ensuring that target architectures directly inform annual IT capital budgeting and project portfolio selection.
• Integration with Project Management Office (PMO): Embedding architecture compliance checkpoints into PMO stage-gate project delivery methodologies (e.g., Waterfall, Agile, SAFe).
• Integration with Solution Delivery & DevOps: Providing reusable architecture building blocks (ABBs), service designs, and API contracts to agile delivery squads.
• Integration with IT Service Management (ITSM): Aligning technology architecture standards with operational service catalogs, incident management, and CMDB assets.