Why EA impact fades (even when the models are beautiful)

Reproduced from a LinkedIn post in February 2026

I have a chat with a consultancy later. Like many organisations, they want their EA practice to have a greater impact.

For years, I’ve believed that presenting EA within a target operating model context is the way to have greater impact and be seen at the board table.

There’s a good story here, e.g. strategy driving capability, but does this create a sustainable change or is it temporary? Are we kidding ourselves, and how can we challenge our thinking here?

You “connect EA to strategy” when the people who run the business and the people who deliver change can use EA to make better decisions faster, and can see that those decisions are traceable

But here’s the uncomfortable question. We’ve “connected EA to strategy”… but have we really?

In most organisations, the “connection” is often logical (maps exist) but not behavioural (decisions don’t change). The connection becomes real only when:

• The exec/business leaders see EA as the instrument panel for strategy execution (options, trade-offs, sequencing, risk), not an IT artefact
• Delivery teams see EA as portfolio design and guardrails that reduce rework and conflict, rather than a gate
• IT strategists and platform leaders see EA as the translation layer that aligns investment, standards, and platform evolution to business outcomes.

So, yes, you can claim “connection” when the models line up. But the real connection is when EA changes what people choose, fund, and stop funding.

This may seem like a grand aim, but these things must happen; choices must be made because of quality thinking. It might be labelled something else (or not happen at all!), but the thinking is largely the same as that of a good EA.

Who needs convincing, and what do they each need to believe? We could think of it as three audiences, each with a different “conversion” moment:

The business or top table doesn’t want enterprise architecture; they want:

• Confidence that the strategy is doable, sequenced, and de-risked.
• Clarity on trade-offs: “If we prioritise X, what do we delay or de-scope?”
• A narrative that links ambition to capability outcomes to investment choices and to an enterprise design that has the unseen capability that makes it viable (via a blending of VSM and EA).

Their belief shift: EA is a business discipline that informs and protects outcomes, not an IT design function.

Delivery leadership (portfolio, programmes, product) needs:

• Constraints and dependencies made visible early (so they can plan, not firefight).
• Patterns/guardrails that allow speed (“right first time”), not bureaucracy.
• Decisions captured and reused so they don’t re-litigate the same issues.

Their belief shift: EA reduces delivery friction and rework; it is not a stage-gate.

IT strategy / platform leadership needs:

• A coherent view of the target state and transition that guides platform evolution.
• Alignment across the technology and data domains rather than parallel ‘towers’.
• Proof that architecture isn’t theoretical, it shapes investment, operating model, outcomes and action.

Their belief shift: EA is the integrator that makes tech strategy legible to the business and usable by delivery teams.

What if we could say these things:

• “We provide a route from strategy to execution design that your exec can use weekly.”
• “We integrate business design, data/information, platforms, and delivery constraints in one coherent decision flow.”
• "We leave behind not just documents but a working governance and community that sustains the connection.”

A useful litmus test is whether EA is changing what gets funded, what gets sequenced, or what gets stopped; if it isn't, it’s not connected to strategy; it’s describing it.

And to connect it, we need to ensure we are enabling leaders to:

• Reduce uncertainty in strategic choices.
• Surface trade-offs early and clearly.
• Make delivery outcomes more predictable and delivery value more transparent.
• Protect value (avoid wasted spend, rework and incoherent investments).

If we build a practice, internal or a consulting practice, around decisions, not artefacts, EA stops being ‘IT architecture’ and becomes the mechanism that helps business leaders choose and sequence investments.

That’s how the business sees relevance, and it’s how we earn a consistent seat around a table we feel we can have the best impact.

To repeat an earlier line. In most organisations, the “connection” is often logical (maps exist) but not behavioural (decisions don’t change). The connection becomes real only when we see those behavioural changes, repeated over time, and become a sustained part of how things get done.

Can I honestly say that every time I have done this work, I have achieved this? No, I don’t think I have. I need to find the missing element that enables this final step.