Enterprise Architecture as a Strategic Function, Not a Documentation Function
Walk into the average enterprise architecture team and you’ll find brilliant people doing useful work that nobody reads. They maintain reference architectures. They run architecture review boards. They produce roadmaps. They publish standards. The work is competent. It rarely changes a business decision.
The diagnosis most EA leaders reach for is: “we need better visualisation,” or “we need to communicate better,” or “we need executive sponsorship.” All true, all symptoms. The disease is structural: enterprise architecture has been positioned as a documentation function inside organisations that need it to be a strategic function.
What ‘documentation function’ means in practice
A documentation function records decisions that other functions make. The decisions about which products to launch, which markets to enter, which technologies to adopt, which vendors to buy from — those happen in product committees, executive committees, technology selection committees, vendor management forums. EA is invited to the meetings to capture the decisions in architecture artifacts.
Done conscientiously, this produces accurate architecture artifacts. Done conscientiously over five years, it produces an EA team that nobody invites to meetings because everyone knows what they’ll be asked to do: document the decision after it’s been made.
The strategic function looks different. In a strategic function, EA is in the room where the decisions are being made, contributing analysis that changes the decision before it’s finalised. The team is small, senior, and respected. Their work is consulted before commitments, not after.
Why the shift is hard
The shift from documentation to strategic function isn’t a tooling change or a methodology change. It’s a positioning change — specifically, a positioning change in the governance forums where decisions actually get made.
In most organisations, decisions flow through three principal forums:
- The Executive Committee. Strategic direction, major investment, M&A. Membership: CEO, CFO, COO, CIO, business unit heads.
- The Investment Committee. Capital allocation, project funding, vendor selection over a threshold. Membership: CFO + delegated executives.
- The Technology Council (or similar). IT strategy, architecture standards, build-vs-buy. Membership: CIO + CTO + senior IT leadership.
In the documentation positioning, EA reports into the third forum and observes the first two. In the strategic positioning, EA contributes analysis to all three.
Why is the shift hard? Because the Executive Committee doesn’t want one more voice in the room. The Investment Committee doesn’t want one more analysis to evaluate. The Technology Council is already full of competing technical perspectives. Adding EA to all three requires displacing something or someone.
The structural move that actually works
The move that works in our experience is not asking for a seat at the existing forums. It’s changing the analysis EA produces, so the existing forums can’t make their decisions without it.
Specifically: every decision that lands in the Investment Committee should be accompanied by an artifact that maps the proposed investment to (a) the business capabilities it builds or modifies, (b) the gaps it closes from the current capability map, and (c) the outcomes those gaps were blocking. We call this a capability impact statement.
When an Investment Committee sees their first three capability impact statements, two things happen. First, they start asking where’s the capability impact statement for this proposal? when one is missing. Second, EA becomes the function that produces them.
Within two quarters, EA is structurally embedded in the Investment Committee’s workflow. Not because EA was given a seat — because the analysis EA produces has become a precondition for the committee’s decisions.
What this requires from the EA team
- A current capability map. Not a wish-list. The actual capabilities the organisation has today, scored on maturity and ownership. Without this, the capability impact statement is fiction.
- A current outcome map. The outcomes the business is being measured on, decomposed into the capabilities they depend on. This is pillar 1 of A2O. Without it, EA can’t connect proposed investments to outcomes the executive committee cares about.
- A maintained gap register. Refreshed quarterly. Without it, EA can’t say which gaps the proposed investment closes, and the impact statement reduces to opinion.
- Senior architects who can write succinctly. A two-page capability impact statement is read. A 40-page architecture review document is filed.
What it requires from leadership
Two things, and only two. First, the CIO has to commit to the capability impact statement becoming an artifact of the Investment Committee’s process. The CFO usually supports this because it produces a more defensible audit trail for spending decisions.
Second, the EA team has to be staffed for it. Most EA teams are staffed to maintain documentation, not to produce strategic analysis. Some EA leaders need to reduce their team and upgrade the seniority of who’s left. This is uncomfortable. It’s also the precondition for the function actually mattering.
What it doesn’t require
It doesn’t require new tooling. The EA repository you have is probably adequate. The visualisation tools you have are probably adequate. The framework (TOGAF, Zachman, custom) you’re using is probably adequate. The structural fix is not about tools or frameworks.
It doesn’t require a CIO who is also a great communicator. It requires a CIO who is willing to insist that capability impact statements become a workflow precondition.
It doesn’t require permission from anyone outside the IT function. The capability impact statement is something EA can start producing tomorrow, attached to every IT investment proposal that goes to the Investment Committee. The committee may ignore the first few. By the fourth, they’ll be reading them.
The outcome
An EA function positioned this way has three concrete characteristics that distinguish it from the documentation positioning.
- Its work product is consulted before commitments, not after. Capability impact statements precede Investment Committee decisions.
- Its budget is connected to outcomes. When the gap register shows a $20M outcome blocked by a capability gap, the EA function can defend the headcount to close the gap.
- It survives leadership change. The artifacts (outcome map, capability map, gap register, capability impact statements) outlive any individual executive. EA doesn’t collapse when the sponsoring CIO leaves.
This is what we mean when we say EA should be a strategic function. The transition is structural — not aspirational. Start with the capability impact statement. Position EA in the workflow where decisions are made. Maintain the artifacts that make EA’s analysis indispensable.
If you’re an EA leader watching your work get filed but not used, the fix is not better diagrams. It’s structural. Attach your analysis to the decisions that get made, in the language those decisions are made in.
WetzEnt helps organisations make this transition through the A2O methodology. Reach out if you’d like to discuss the move.