Your operating model is the real legacy system

For the past decade, enterprise modernization has been framed as a technology problem.

Legacy systems. Technical debt. Monoliths that need to be broken apart and moved to the cloud.

That framing is convenient and also incomplete.

In most organizations, the technology isn’t the constraint. The operating model is.

You can see it in how decisions move — or don’t. A product team identifies an opportunity. It makes its way through architecture review, risk, finance and multiple layers of approval. Each step is rational on its own. Collectively, they create latency.

By the time a decision is made, the opportunity has changed.

This is rarely called out as the primary issue. It gets labeled as “complexity” or “scale.” But the pattern is consistent. The system isn’t slow because the technology can’t move. It’s slow because the organization can’t decide.

That distinction matters.

Most modernization programs focus on replacing systems of record. They invest in platforms, APIs and cloud infrastructure. The expectation is that once the technology is up to date, the business will move faster.

But the underlying decision structure remains unchanged.

Funding is still annual and project-based. Authority is still fragmented across functions. Accountability is distributed in a way that makes outcomes ambiguous. Risk is still evaluated in isolation, rather than in the context of business intent.

So, the organization implements modern technology on top of a legacy operating model.

The result is predictable.

Speed doesn’t increase. It fragments. Teams move quickly in isolated pockets while enterprise decisions continue to stall. The organization appears more active, but not more effective.

This is where many transformation efforts quietly lose momentum.

Most organizations don’t recognize it at the time. It just feels like things are taking longer than they should.

From the outside, progress is visible. Systems are upgraded. Agile is adopted. Cloud adoption metrics improve. But inside the organization, the experience is different. Decision cycles are still long. Dependencies are still opaque. Tradeoffs are still negotiated too late.

The operating model absorbs the change and neutralizes it. McKinsey has observed the same pattern in operating model transformations: The organization starts to change, but under pressure, decision-making fragments, accountability weakens and the system defaults back to how it has always operated.

This is why some of the most heavily invested technology environments still struggle to produce consistent business outcomes.

The issue isn’t capability. It’s coordination.

Even at the CIO level, the pattern is getting harder to ignore: AI doesn’t create value. Organizations do, and most aren’t structured to do it consistently.

In practice, the operating model defines how work gets prioritized, how decisions get made and how tradeoffs are resolved. It determines whether the organization can convert technology capability into business results.

When that model is misaligned, even well-executed technology initiatives underdeliver.

You can see this most clearly in how organizations handle cross-functional decisions.

A customer experience initiative spans multiple systems, teams and risk domains. Each group operates with its own priorities and constraints. There is no single point at which trade-offs are made with full context.

So, decisions are escalated, deferred or negotiated incrementally.

Nothing breaks. But nothing moves with intent.

Over time, this creates a form of structural drag. Not visible enough to trigger intervention, but persistent enough to erode performance.

Organizations respond by adding more process. More governance. More coordination layers.

The system becomes more controlled, but not more effective.

That same pattern shows up in execution. It doesn’t collapse; it fragments. Alignment fades, coordination weakens and progress slows despite the capability being there. This is a failure mode McKinsey has also highlighted in its work on digital and AI transformation.

This is the paradox many CIOs are now navigating. Technology has advanced to the point where it can support far more adaptive, responsive businesses. But the way the enterprise is structured for decision-making hasn’t kept pace.

So, the constraint has shifted.

It’s no longer primarily in the systems.

It’s in the way the organization operates those systems.

This is also why comparisons between companies in the same industry can be misleading. Two firms may run similar technology stacks, use the same cloud providers and invest at comparable levels.

Yet their outcomes diverge.

One moves with clarity, the other stalls under its own weight.

The difference is not the technology.

It’s how decisions are made, who owns them and how quickly they can be executed.

That is the operating model.

And in many enterprises, it is now the oldest system in the environment.

It carries forward assumptions about control, risk and coordination that were designed for a different era. An era where change was slower, systems were more centralized and decisions could be sequenced over time.

That environment no longer exists.

But the model remains.

So, organizations continue to invest in modern technology while relying on a legacy structure to use it.

The gap between what the technology can do and what the organization can execute continues to widen.

At a certain point, that gap becomes the defining constraint on performance.

Not because the systems are outdated.

But because of the way the enterprise operates them.

This article is published as part of the Foundry Expert Contributor Network.
Want to join?