The Architecture Capability Framework: Building a Mature EA Team

After you've mapped your career and understood digital transformation, the next question is: "How does an organization build a professional Enterprise Architecture (EA) function?"

Enterprise Architecture is not something that just "happens." It requires a structured set of people, processes, and tools to be effective. This is what TOGAF calls an Architecture Capability.

In this post, we’ll explore the Architecture Capability Framework and how you can use it to build a mature, high-performing EA team.

What is an Architecture Capability?

Think of an "Architecture Capability" as the Enterprise Architecture Engine of the company. It’s what allows the organization to take a business strategy and turn it into a successful technical reality.

The Capability Framework is mostly handled in the Preliminary Phase of the ADM. This is where you set the "rules of the game" before you start designing anything.

The Four Pillars of the Capability Framework

To have a functioning EA capability, you need four things:

Structure: The organizational chart. Who is in the team? Who do they report to?
Process: The TOGAF ADM itself. How does the team actually do its work?
People: The skills and experience of the architects.
Tools: The software repository, standards, and repositories (the Architecture Repository).

The Architecture Board: The Governing Body

A mature EA capability needs an Architecture Board. This is the formal committee that oversees and governs all architectural activity.

The Board's Core Tasks

Approve Strategic Designs: Ensuring the company is moving in the right direction.
Grant Waivers: Deciding when a project can deviate from a technical standard (e.g., "for this specific emergency project, you can use MySQL instead of PostgreSQL").
Manage Compliance: Checking that building teams are actually following the approved designs.
Dispute Resolution: Resolving conflicts between different technical teams.

An EA team without an Architecture Board is just a group of advisors with no real authority.

Measuring Success: The Architecture Maturity Model

How do you know if your EA team is doing a good job? Many organizations use a Maturity Model (often based on CMMI).

The Five Levels of EA Maturity

Level 1: Initial: No formal architecture process. Decisions are made on a project-by-project basis.
Level 2: Under Development: Some basic standards exist, but the process is not consistently followed.
Level 3: Defined: A formal EA team exists, the TOGAF ADM is used, and a repository is in place.
Level 4: Managed: The EA team is measuring its own performance and ROI. Metrics are used to drive improvements.
Level 5: Optimizing: The EA capability is "self-healing." It continuously improves based on real-world feedback and changing business needs.

As an architect, your goal is to move your organization up at least one maturity level every 1-2 years.

Summary

Building an Enterprise Architecture capability is a marathon, not a sprint. It takes time to build the trust, the processes, and the tools needed to truly influence an organization. By using the Architecture Capability Framework, you can ensure your team is built on a solid foundation, with the authority and the skills to deliver real strategic value.

In our next post, we’ll see how this looks in the real world with: TOGAF Case Studies — FinTech, Healthcare & Retail.

This post is part of the TOGAF 9.2 Masterclass series. Don't forget to check out our previous post on Digital Transformation with TOGAF — Agile EA.