Why Transformations Struggle: It’s Not the Tech — It’s the Operating Model

1. A Familiar Pattern: When the Technology Works but the Change Doesn’t

Many transformation initiatives follow a reassuringly familiar path...

Systems are implemented successfully. New capabilities are technically available. Delivery milestones are met. Training is completed and communications are issued. On paper, the transformation appears to be progressing exactly as planned.

And yet, months later, the results feel underwhelming. Benefits arrive more slowly than expected. The value case feels harder to evidence. Old workarounds quietly resurface, and leaders sense that, despite all the activity, the organisation hasn’t fundamentally shifted.

A common conclusion follows: the technology hasn’t delivered.

But in many cases, that conclusion doesn’t quite hold. The technology often does exactly what it was designed to do. What proves more difficult is the organisation’s ability to absorb it.

This disconnect is not unusual, and it is not always a sign of poor execution or weak intent. Well-run programmes with capable teams can still struggle to convert delivery success into lasting business change.

Understanding why that happens requires looking beyond the technology itself.

2. Why Technology Is So Often Blamed

It would be unrealistic to claim that technology is never the issue. Sometimes the wrong solution is selected. Sometimes tools are immature or oversold. And sometimes there is genuine resistance to change.

However, focusing solely on these explanations can obscure a deeper and more persistent pattern. Even when the technology is sound and delivery is competent, transformations can still struggle — because the operating model was never designed to support the change being introduced.

Technology is an easy focal point. It is visible, measurable, and expensive. It comes with contracts, vendors, and clearly defined deliverables. When outcomes disappoint, it provides a tangible place to direct frustration.

Structure, governance, incentives, and behaviour are far less visible. They are harder to measure, slower to change, and often taken for granted. As a result, they receive less scrutiny — even though they shape how work actually happens every day.

This leads to a useful distinction:

Technology changes what is possible.

Operating models determine what is probable.

Until that distinction is recognised, organisations risk repeatedly investing in new capabilities while relying on operating models that were optimised for a different way of working.

3. What an Operating Model Really Is (in Practice)

Operating models are often discussed in abstract terms, but their impact is felt in very practical ways.

An operating model describes how an organisation translates strategy into everyday action. It shapes how work gets done, how decisions are made and escalated, who owns outcomes, how teams are structured and measured, and how change is absorbed once delivery activity ends.

In other words, an operating model is the system that turns strategic intent into behaviour.

During periods of stability, operating models tend to fade into the background. They evolve incrementally and are rarely questioned. Transformation disrupts that equilibrium.

As new capabilities are introduced and expectations shift, the assumptions embedded in the operating model are exposed. Ways of working that were previously effective begin to create friction. Decision-making slows. Accountability blurs. Informal workarounds multiply.

Crucially, operating models often change far more slowly than the technology they are expected to support. When this happens, organisations are left trying to deliver new outcomes using structures designed for the old world.

4. Operating Model Gaps That Commonly Undermine Transformation

When transformations struggle, it is rarely due to a single flaw. More often, a series of operating model gaps combine and compound over time.

These gaps do not always cause transformations to fail outright. But they frequently explain why momentum slows, benefits leak, and confidence fades — even when delivery appears successful.

Decision rights don’t match the change being introduced

As organisations introduce new capabilities, decision-making often needs to become faster and closer to the work. In practice, governance structures frequently remain slow, centralised, or ambiguous. Ownership is fragmented, and escalation replaces accountability.

The result is predictable. Decisions take longer than the environment allows. Teams wait for approvals, work around formal processes, or push issues upward. Leaders become frustrated by what feels like a lack of ownership or urgency.

The organisation has invested in speed, but is still designed for control.

Roles haven’t evolved, even though the work has

Transformation introduces new responsibilities, dependencies, and expectations. Yet role definitions often remain unchanged. Accountability for outcomes sits uncomfortably between delivery teams, operational management, and senior leadership.

Delivery completes, systems go live, and unresolved issues persist. Questions about ownership linger. Over time, outcomes erode quietly rather than failing dramatically.

Transformation often fails quietly when responsibility for outcomes is never clearly owned.

Processes are optimised for stability, not change

Many organisational processes were designed to maximise predictability, control, and risk minimisation — often with good reason. During transformation, those same processes can become sources of friction.

Learning slows. Decisions are delayed. Progress increasingly depends on individual effort and informal workarounds rather than system support.

Processes that once protected performance can unintentionally prevent progress.

Change is treated as an event, not a capability

Change is frequently approached as something to be delivered: training completed, communications issued, go-live achieved. Less attention is given to whether the organisation has developed the capability to operate differently over time.

People are expected to adapt, but incentives, measures, and support structures remain largely unchanged. What is labelled resistance is often a rational response to a system that still rewards old behaviours.

When change appears to be resisted, it is often worth asking whether the organisation has actually made the new way possible.

Local optimisation erodes enterprise value

Teams and functions continue to optimise for their own objectives and measures. Trade-offs across boundaries remain implicit or unresolved.

The result is fragmented benefit realisation. Local success undermines enterprise outcomes, and leaders struggle to capture the full value of the transformation.

Transformation exposes misalignment that already existed — it doesn’t create it.

Individually, these gaps create friction. Combined, they compound risk.

As transformation increases pace and complexity, operating model weaknesses surface earlier, more visibly, and with greater impact. This is often the point at which attention turns back to the technology — even though the underlying issues lie elsewhere.

5. How Technology Exposes These Gaps (Rather Than Causing Them)

Technology rarely breaks transformations. More often, it reveals how the organisation already works.

A useful way to think about this is that technology accelerates whatever an organisation already is. It increases pace, visibility, and interconnectedness. In doing so, it brings underlying operating model weaknesses to the surface.

• Automation exposes unclear ownership and decision rights.

• Data platforms surface inconsistent definitions, fragmented accountability, and unresolved trade-offs.

• AI highlights ambiguity in processes, policies, and judgement that was previously absorbed by people and workarounds.

• Digital tools clash with governance structures designed for slower, more hierarchical environments.

In each case, the technology is not creating new problems. It is removing the buffers that previously allowed existing problems to remain hidden.

This is why technology is so often blamed when transformations struggle. It is where friction becomes visible first — even when the root cause sits elsewhere.

6. What Successful Transformations Do Differently

Organisations that navigate transformation more effectively tend to approach the operating model deliberately rather than implicitly.

They consider how decisions will be made before speed becomes critical. They clarify ownership for outcomes, not just delivery. They allow roles, governance, and incentives to evolve as ambiguity reduces and learning increases.

Rather than treating change as something to be completed, they treat it as a capability to be developed. Support structures are put in place. Measures are adjusted. Space is created for adaptation rather than forced compliance.

Importantly, these organisations do not expect the operating model to catch up on its own. They shape it intentionally to support the future state they are trying to create.

7. Closing Reflection: Is Change Really Being Resisted?

When transformations struggle, it is tempting to conclude that the technology was flawed or that people resisted the change. Sometimes that is true. Often, it is incomplete.

A more useful question is whether the organisation made it possible for people to work in the new way. Were decision rights aligned to the change? Were incentives adjusted? Were roles and processes designed to support different behaviours?

Seen through this lens, what looks like resistance is frequently a signal of deeper structural misalignment.

If a transformation is not delivering the outcomes expected, it is often worth asking not why people are unwilling to change, but what the operating model is making difficult or impossible.

Better still, incorporate operating model design early in your next transformation to support the cultural change needed to deliver the desired outcomes. When operating models evolve alongside technology, transformation moves beyond delivery — and becomes durable.