Enterprise Architecture Value Model

Before you can advance your architecture function, you need an honest understanding of why the traditional model produces the organizational outcomes it does — and why those outcomes are structural rather than a reflection of the capability or commitment of the practitioners within the function.

The dominant model for enterprise architecture since the discipline emerged as a formal function has been advisory. Frameworks like TOGAF — among the most widely referenced in the industry — are organized almost entirely around the production of architectural artifacts: frameworks, reference models, catalogs, matrices, governance documents, and views that describe the enterprise’s technology landscape and the principles that should govern its evolution. The assumption embedded in this model is that producing high-quality architectural documentation, enforcing standards through governance gates, and advising delivery teams on architectural decisions is sufficient to generate organizational value and justify the architecture function’s existence.

In practice, most architecture functions are not implementing any governance framework at anything approaching its full scope. They are firefighting — responding informally to initiative work, participating in design reviews for complex programs, and trying to maintain some semblance of standards governance in the margins of their actual work. The comprehensive, consistently curated architectural knowledge management capability that the advisory model envisions is, in most enterprises, a permanent future state. Architecture repositories accumulate artifacts that nobody reads, standards that nobody enforces, and models that nobody updates. The expensive Architecture Modeling Tools that were supposed to make this manageable get decommissioned when the cost-benefit calculation cannot be made to work — and it typically cannot, because the value those tools produce is not visible in the terms that control their license budget.

Your architecture function remains at Levels 1 or 2 not because your architects lack skill or commitment. It remains there because the advisory model is what the function was designed to do. Moving it forward requires a deliberate organizational decision — one that you, as the IT leader, are the only person in the organization with the authority to make.