The Operating Model is the New Constraint

The conventional wisdom in enterprise modernization holds that legacy systems and technical debt are primary bottlenecks. While these certainly exist, a growing number of organizations find that technology represents only part of the challenge.

In reality, many enterprises struggle not because their technology can’t move faster, but because their organizational structure prevents decisions from being made efficiently. A product team identifies an opportunity, and it gets routed through multiple layers of review—architecture, risk, finance—before reaching a decision point. Each step seems reasonable in isolation, yet collectively they create significant latency.

This pattern manifests as “complexity” or “scale,” but the root cause is often a fragmented decision-making process that prevents timely responses to changing market conditions.

The Modernization Paradox

Most modernization programs focus on upgrading systems of record and implementing new platforms. While these investments improve technical capability, they frequently fail to deliver anticipated speed gains because the underlying operating model remains unchanged:

• Funding continues to be allocated through annual project cycles
• Authority is fragmented across functional silos
• Accountability for outcomes is diffused
• Risk assessments occur in isolation from business context

The result is a familiar paradox: organizations implement modern technology on top of legacy structures, creating isolated pockets of agility within an otherwise constrained environment.

From Capability to Outcomes

McKinsey research has observed this pattern repeatedly—the organization starts to transform, but under pressure reverts to established operating norms. This explains why some companies with cutting-edge technology still struggle to generate consistent business results.

The constraint has shifted from technical capability to organizational coordination. Even at the CIO level, leaders are realizing that AI and other transformative technologies don’t create value on their own—well-structured organizations do, and most aren’t currently designed for this purpose.

The Structural Drag

Cross-functional initiatives often highlight this disconnect: a customer experience project might span multiple systems, teams, and risk domains, with no single point of accountability for trade-offs. Decisions get escalated or negotiated incrementally, creating what one consultant termed “structural drag”—not visible enough to trigger intervention, yet persistent enough to erode performance.

Organizations respond by adding more process and governance, which further controls activity without necessarily improving effectiveness.

The solution isn’t simply adopting new technology; it’s redesigning how decisions are made, who owns them, and how quickly they can be executed—in essence, modernizing the operating model to match the potential of the digital investments.