The Operating Model Conversation Enterprise Architecture Keeps Avoiding

Most EA friction isn't a governance problem. It's a misalignment problem.

There is a pattern I have seen play out. An Enterprise Architecture team, doing its job diligently, pushes a business unit to standardise and unify its processes. The business unit resists. The EA team escalates. Relationships deteriorate.

Everyone involved believes the other side is being unreasonable.

Often, neither side is. The real problem is that nobody sat in a room and agreed — at the enterprise level — on how the organisation is actually supposed to operate.

That conversation has to happen before EA can be effective. Without it, architecture becomes a political instrument rather than a strategic one.

The Framework That Changes the Conversation

Enterprise Architecture as Strategy presents a simple 2×2 framework built around two axes: standardisation and integration.

The four models are:

Diversification — low standardisation, low integration. Business units operate autonomously, with distinct customers, products, and processes. Corporate value comes from brand, capital allocation, and selective shared services, not from integrated operations. Think conglomerate. Think private equity portfolio. Autonomy is not a bug here — it is the design.

Coordination — low standardisation, high integration. Units share customers, products, or data, and that shared visibility matters enormously. But local processes remain varied, because the differences between units are real and worth preserving. The integration is data-deep, not process-wide.

Replication — high standardisation, low integration. A proven operating format is replicated consistently across largely independent units. The value is in operational efficiency and the speed at which a working model can be deployed. Units are not interdependent — they are parallel.

Unification — high standardisation, high integration. Tightly coupled units, common processes, shared data, maximum scale efficiency. This is the model that EA naturally gravitates toward recommending. It is the right answer for some organisations. It is the wrong answer for more than most EA teams realise.

The Friction Has a Name

When EA pushes a Diversification business unit toward Unification, the business unit resists — not because it does not understand architecture, but because the recommendation is genuinely wrong for its context.

The unit has been designed to operate independently. Its customers are different. Its products are different. Its market dynamics are different. Forcing it onto common processes and shared platforms does not create efficiency. It destroys the very flexibility that makes the unit competitive.

The EA team is not wrong that standardisation and integration have value. But they are

applying a framework designed for a Unification model to an organisation that has chosen — whether explicitly or by accumulated history — to operate at Diversification.

That is not a technology problem. It is a strategy problem.

The Agreement That Has to Come First

The operating model choice belongs at the enterprise level. It is a decision for business and technology leadership together — not a conclusion that EA arrives at independently and then attempts to enforce.

Once that choice is made and genuinely agreed upon, everything downstream from it changes. EA's role, priorities, and boundaries become clear. The authority to standardise — or not — is understood by all parties. Business unit leaders know what autonomy they retain and what they are expected to surrender. The governance conversations stop being political and start being structural.

Without that agreement, EA operates in a vacuum.

Different operating models can legitimately coexist at lower levels of the organisation. A Coordination model at the enterprise level does not prevent individual functions from pursuing Replication within their own boundaries. But the enterprise-level choice must be made first. It shapes everything: the role of IT, the scope of EA, the degree of autonomy available to business unit leaders, and the design principles that govern technology investment.

What This Means in Practice

The first conversation worth having is not about architecture standards. It is about the operating model.

If your Enterprise Architecture team is constantly fighting for compliance, constantly meeting resistance from business units, and constantly rebuilding the case for standardisation that never quite lands — this is usually the diagnosis. The operating model was never agreed. EA is pushing in one direction. The business is organised to pull in another.

That tension will not be resolved by better governance frameworks or more robust review processes.

It will be resolved by a conversation that should have happened earlier — and that it is never too late to have.

Where Noetrix Comes In

At Noetrix, this is exactly the kind of conversation we facilitate. Not another architecture review. Not another governance framework. A structured, senior-level alignment session that gets business and IT leadership in the same room, working from the same operating model.

If your EA programme is stalling, or you are about to invest in a major transformation and want to get the foundations right before the spend begins — we would like to talk.

Schedule a call→

Dushyant Bhardwaj is the Founder and Fractional CTO of Noetrix Consulting. With over 25 years of technology leadership across startups and FTSE 100 enterprises, he works embedded with CIOs, CTOs, and boards to turn complexity into clarity.

Source: Enterprise Architecture as Strategy