Enterprise architecture earns influence through decisions
An effective architecture practice helps leaders compare options, understand consequences, and commit to a course of action.
Enterprise architecture earns influence when it improves a decision that matters to the business. That requires architects to understand the problem, explain the options, and make a reasoned recommendation. Technical depth remains essential; the work becomes more valuable when that depth informs a choice leaders need to make.
My earlier essay examined Gartner’s argument for an internal management consultancy model of enterprise architecture. I see its practical value in a service orientation: architecture work begins with a business need and produces advice people can act on.
Begin with the decision
An architecture engagement needs a clear question. A business entering a new market may need to decide which capabilities to develop internally and which to obtain through partners. A team struggling with fragmented customer service may need to resolve ownership and information gaps before selecting a platform.
These questions call for different evidence and different models. Architects should select the views that explain the problem rather than presenting every available model. A capability map, value-stream view, or dependency analysis becomes useful when it makes an important consequence visible.
Advise with a point of view
A useful recommendation states what should happen, why it should happen, and what would make the recommendation change. It makes assumptions visible and explains the trade-offs. Leaders should be able to see the implications for cost, risk, delivery, people, and the wider enterprise.
For an illustrative platform decision, the architect might recommend a shared service because several business units require the same capability. That recommendation should also address the service owner, funding, adoption effort, and limits on local variation. Without those arrangements, the technical recommendation is incomplete.
Co-creation improves the advice. Operating teams know where work breaks down. Finance can challenge the economics. Security and technology teams can test feasibility. The architect’s contribution is to connect those perspectives and expose conflicts that a single department may miss.
Keep governance connected to value
An advisory approach still needs standards and governance. Those mechanisms protect reliability, interoperability, and the organisation’s ability to change. The aim is to explain their business purpose and make exceptions deliberate, with owners and review dates.
Measure the practice through the decisions it improves and the outcomes it helps enable. Useful evidence includes an avoided duplication, a resolved dependency, a clearer investment sequence, or a service that delivers its intended benefit. Document the contribution without claiming sole credit for results produced by many teams.
Architecture becomes a leadership discipline through this sustained work: understanding the enterprise, exercising judgment, and helping people make coherent decisions together.
Revised from my original essay on The Loop. This edition develops the argument for a leadership audience; the original preserves its coursework context and bibliography.
Original article: The Loop, 2 November 2025.