If Enterprise Architecture is not influencing investment and prioritisation decisions, it is operating too late. Embed architecture in early-stage discussions where options are still open, and replace large artefacts with targeted views that directly support a specific decision.
Enterprise Architecture does not lack capability. It often lacks position, relevance at the right moment, and earned trust.
I have been thinking a lot about why Enterprise Architecture still struggles to be truly felt by the business.
Not challenged. Not rejected.
Just not consistently seen as essential.
Part of the reason is that EA is not like finance, legal, or HR.
Those functions are deeply embedded into organisations. Their place at the table is unquestioned because their value is universally understood.
Enterprise Architecture is different.
Its seat is not guaranteed.
It has to be earned continuously.
And honestly, that is fair.
How Enterprise Architecture Drifted
Over time, Enterprise Architecture became heavily associated with technology:
- systems
- standards
- governance
- tooling
- architecture artefacts
That shaped the perception many businesses still hold today:
EA is primarily an IT function.
But the original intent was always much broader.
Enterprise Architecture should sit at the intersection of strategy, operating model, investment choices, technology direction, organisational change, and delivery reality.
When it is reduced to technical governance or documentation, the business naturally sees it as something useful but not essential.
The Visibility Problem Is Really a Positioning Problem
Many EA teams try to solve this by producing more artefacts, running more forums, or asking for a stronger mandate.
Those things can help, but they do not solve the core issue.
If Enterprise Architecture is not close to the decisions that shape investment and priority, it will always be seen too late.
By the time a solution is already funded, scoped, and politically committed, architecture advice can feel like friction. It arrives after the moment where it could have created the most value.
The practical shift is to move EA closer to where options are still open and decisions are still being formed.
A Practical Shift
Improving impact does not require Enterprise Architecture to become louder. It requires EA to become more useful at the point of decision.
1. Earn Trust Through Practical Value
Enterprise Architects should not demand strategic influence. They should earn it by consistently helping leadership:
- simplify complexity
- expose trade-offs
- connect strategy to execution
- bring clarity to change
2. Replace Large Artefacts With Targeted Views
Large models and documents have their place, but decision-makers rarely need the full architecture story at once.
They need a clear view of the choice in front of them: what changes, what it depends on, what it enables, what it risks, and what must be true for the decision to work.
3. Connect Architecture To Organisational Direction
EA becomes more visible when it is tied to the language of the organisation: outcomes, capability, risk, investment, sequencing, and delivery confidence.
That does not mean abandoning technical depth. It means translating that depth into decision support.
Final Thought
Enterprise Architecture does not need to become louder.
It needs to become more trusted, more connected to organisational direction, and more useful at the moment decisions are being made.
That is how EA becomes visible for the right reasons.
Comments and thoughts
Share your thoughts on this topic, or leave a question.
Loading comments...