Has Business Architecture Become the New PMO?

Deepak Mohan

19 Sep 2025 — 2 min read

A controversial thought: in many organisations, Business Architecture has quietly taken on the role of PMO. Instead of serving as the wide-angle view on value, strategy, and future competitiveness, it often becomes:

Gatekeepers of governance.
Creators of flashy capability maps that gather dust.
A reporting layer that slows down delivery instead of helping it.

This was never the intent of the discipline. At its core, Business Architecture is meant to provide a complete view of how an enterprise delivers value. It connects strategy to execution, aligns capabilities with outcomes, and reshapes how organisations respond to changing markets.

Yet here lies the tension.

Why executives don’t get it

Many senior leaders simply do not understand Business Architecture. Worse, they often do not even try.

They focus on traditional management practices that emphasize short-term delivery, tackling immediate issues, and silo-driven accountability. To them, a Business Architect asking about value streams, capabilities, and operating models feels “academic” or “obstructive.”

The executive mindset is:

“We need to deliver this program now; don’t slow us down with frameworks.”
“Capabilities and value streams? Just give me a plan and budget.”
“We already have a PMO; why do we need another layer?”

As a result, Business Architecture gets lumped into PMO or Solution Design functions. The distinct enterprise perspective is lost.

The danger of becoming PMO 2.0

If Business Architecture becomes too entrenched in program management, it risks becoming just:

An expensive governance mechanism.
A policing function that checks alignment after the fact.
A box-ticking exercise that meets compliance but offers little strategic value.

And once that perception takes hold, executives will ask: “Why do we need Business Architects at all?” This is dangerous. Because in reality, Business Architecture is not about slowing down delivery; it is about ensuring delivery creates the right value.

A fork in the road

Here’s the challenge:

Should Business Architecture stay independent, protecting the enterprise view—even if that makes it unpopular with executives who prefer quick tactical wins?
Or should it integrate into delivery, proving its value in the trenches—but risk being absorbed and seen as just another PMO function?

Neither choice is without risk.

If we remain independent, we must find new ways to show our value—speaking the language of outcomes, not artifacts.

If we integrate into delivery, we must protect the strategic voice that makes Business Architecture special.

Time for a reckoning

Business Architecture is at a turning point. Executives are impatient. Delivery demands are high. Yet, without a complete enterprise view, organizations risk piling on short-term fixes that deepen structural debt.

So I leave you with this question: In your organization, is Business Architecture still a strategic enabler or has it become just another PMO in disguise?

I suspect the answers will reveal a lot about how organizations view transformation today.

Why I Called This Site Organised Friction

There is a moment I have encountered in almost every transformation programme I have worked on. It happens in a workshop, or a design review, or sometimes in a corridor conversation that nobody planned. Someone asks a question that stops the room. Not a hostile question. Not a political one.

Iran War: A Geopolitical Shock is the Operating Model Test Most Firms Underestimated

Before I turn to the professional analysis in this article, I want to be honest about the context. The conflict that began on 28 February 2026 has cost thousands of lives. But its consequences have reached into the daily lives of people far beyond the conflict zone. Fuel rationing has

Skills Debt: The Organisational Debt Nobody's Measuring (Organisation Debt Series IV)

In this series I have argued that organisation debt — the accumulated cost of poor structures, deferred decisions, broken processes, and ungoverned data — is a real liability that belongs on the management agenda alongside financial and technical debt. In Part II, I introduced a practical taxonomy: Decision Debt, Control Debt, Data

Your Organisation Has an AI Operating Model. It Just Doesn't Know It Yet

Ask a senior executive whether their organisation has an AI operating model and the answer will almost certainly be: “We’re working on it.” They are wrong. The model already exists. It is just not the one anyone designed. Over the past two years, most organisations have accumulated a sprawling,