Part 3 of 4 Hidden Friction in Organisations: The Real Reason Transformation Doesn’t Stick

Why do transformation programmes keep repeating?

Every few years, a new transformation begins.

New strategy. New structure. New systems. New partners. New language.

And for a moment, it feels like progress.

But then something happens.

• Execution slows again

• Teams fall out of sync

• Decisions stall

• Costs creep back in

• Growth doesn’t follow

And before long… another transformation begins.

This isn’t a failure of effort

Organisations are not short of:

• investment

• capability

• intelligence

• partners

• intent

In fact, most enterprises have spent millions often billions trying to fix this.

So the question isn’t:

“Why aren’t we trying hard enough?”

The real question is:

Why do these efforts not stick?

The uncomfortable truth

Most transformation programmes are designed to:

• change structure

• introduce new systems

• roll out new processes

• align to a new strategy

But they rarely address: how the business actually works day to day. How hidden friction in organisations actually shows up

• how decisions really get made

• where ownership actually sits

• how teams really interact

• where friction actually lives

So the transformation layers on top of the existing system…instead of fixing the system itself.

The 5 reasons transformation programmes fail (ignoring the hidden frictions in organisations)

The real issue is hidden friction in organisations, the gaps between how the business is designed and how it actually operates.

1. They solve for symptoms, not root causes

Transformation often starts with visible problems:

• slow growth

• inconsistent execution

• rising costs

• poor conversion

So the response is:

• new tools

• new structures

• new initiatives

But these are outputs of deeper issues, not the cause.

The real problems sit underneath:

• unclear decision rights

• fragmented ownership

• misaligned incentives

• broken handoffs

Without addressing these, transformation becomes:

a more sophisticated version of the same problem

2. They are designed in isolation from reality

Transformation programmes are often:

• centrally designed

• consultant-led

• model-driven

But the business doesn’t operate in models.

It operates in:

• messy handoffs

• local workarounds

• informal decisions

• historical behaviours

So what gets designed:

• looks coherent on paper

• but doesn’t survive contact with reality

And teams revert back to how things actually work.

3. They underestimate organisational complexity

Modern enterprises are not simple systems.

They are:

• global

• multi-layered

• cross-functional

• politically complex

Transformation often assumes:

• alignment can be designed

• behaviour will follow structure

• change will cascade cleanly

In reality:

• different regions interpret differently

• functions optimise locally

• incentives conflict

• priorities shift

So instead of alignment, you get: controlled fragmentation

4. They don’t change how decisions are made

This is one of the biggest gaps.

Most transformations focus on:

• strategy

• structure

• systems

But not: decision-making

So what happens?

• decisions still escalate

• approvals still loop

• ownership is still unclear

• trade-offs still aren’t made

And without fixing decision-making: execution never improves

Because execution is simply: decisions made consistently at scale

5. They don’t embed a way of working

Even when transformation delivers:

• new processes

• new frameworks

• new playbooks

They often don’t become: how the business actually runs

Instead:

• they sit alongside existing ways of working

• adoption varies by team

• behaviours drift over time

So the organisation ends up with:

• multiple ways of working

• none of them fully embedded

And slowly… everything returns to how it was

The transformation loop

This is why organisations get stuck in a cycle:

1. Identify problems

2. Launch transformation

3. Implement changes

4. See partial improvement

5. Drift back into old patterns

6. Start again

Each cycle adds:

• more tools

• more complexity

• more cost

But doesn’t resolve: the underlying system

So what should organisations do instead?

This is where most thinking jumps straight to:

• “What’s the new model?”

• “What’s the next transformation?”

But that’s the wrong starting point.

1. Start with diagnosis, not design

Before changing anything, understand:

• how work actually flows

• where friction actually sits

• where value is leaking

• how decisions actually happen

Not what should happen.

What actually happens.

2. Make the invisible visible

Most friction exists because it’s hidden.

You need to surface:

• decision loops

• duplicated work

• ownership gaps

• misaligned incentives

Once visible:

• they can be addressed

• trade-offs can be made

• priorities become clearer

3. Fix decision-making first

Before changing structure or systems:

• clarify decision rights

• define ownership

• reduce escalation

• create consistent cadence

Because when decisions improve: execution follows

4. Work with the business you have

Not the one you wish you had.

That means:

• accepting legacy systems

• working within constraints

• designing for real behaviours

Not ideal ones.

Pragmatism beats perfection

5. Embed one way of working

Not another framework.

Not another layer.

One consistent way of working across:

• teams

• regions

• functions

So the business can:

• move together

• decide together

• execute together

This is not about stopping transformation

Transformation isn’t the problem.

How we approach it is

If transformation continues to:

• ignore how the business actually works

• focus on outputs not causes

• add layers instead of removing friction

Then the cycle will continue.

Final thought

Most organisations don’t fail because they lack ambition.

They struggle because: they are trying to fix complexity without first understanding it

Transformation should not start with change. It should start with truth.