The Viscosity Trap: Why Some Organisations Can’t Let Go

What Is Organisational Viscosity?

Viscosity is a term borrowed from fluid dynamics, it describes how much a substance resists flow.
Honey has high viscosity. Water has low viscosity. Air even lower.
In organisations, viscosity describes how tightly current structures, systems, and behaviours cling to the past, even when the future is well-articulated.
It’s not resistance.
It’s resonance with the previous system.
You can change the language.
You can update the charts.
But if the scaffolding underneath remains, change gets absorbed rather than activated.

What Causes It?

In my consulting work with CIOs and strategy leaders, and in my ongoing doctoral research, I keep encountering five core contributors to organisational viscosity.

1. Architectural Inertia
   

   Systems are still optimised for yesterday’s value chains and decisions.
   

2. Incentive Drag
   

   Teams are still rewarded for behaviours the new strategy is trying to de-emphasise.
   

3. Legacy Roles
   

   Job scopes remain rooted in a previous org chart, not in future outcomes.
   

4. Slow Governance
   

   The people with the power to unblock change still meet quarterly and still ask the wrong questions.
   

5. Cultural Echo
   

   Even after a strategy is replaced, the language and logic of the old one persist in meetings, habits, and heuristics.
   

   
   

Organisations forget slowly and act accordingly.

Viscosity Isn’t Always Bad

Some viscosity protects against chaos.
That’s where transformation fails, because the environment couldn’t let it move.
When in reality, it never stood a chance of flowing.

It holds quality standards. It prevents overreaction. It preserves identity.

But too much viscosity in the wrong places?

And worse: the strategy gets blamed for not “landing.”

How to Spot the Viscosity Trap

If you hear phrases like these, you’re probably already inside it:
They’re signals that viscosity is at work.
The system is still shaped for the last strategy.

• “That’s not how our process works.”

• “We tried that before, and it didn’t stick.”

• “Let’s pilot it in one region first… and revisit next quarter.”

• “People are on board,they just need time.”

These aren’t objections.

They’re signals that viscosity is at work.
The system is still shaped for the last strategy.

The Strategic Role of Architecture

This is where Strategic Architecture becomes essential, not as a documentation exercise, but as a design discipline.

Architecture isn't just IT.

It’s how your organisation is set up to behave.

If your current flows, governance, tools, and incentives are still optimised for the prior context, strategy will stall no matter how inspired it sounds.

Design the Value Stream Operating Model for Flow

The opposite of viscosity isn’t chaos.

It’s strategic flow: the ability for intent to move cleanly through a system.

This requires friction-aware design.

It means knowing where to loosen and where to hold firm.
It’s not change management, it’s strategic engineering.

If you’ve ever watched a great strategy underwhelm in execution,
don’t assume it was flawed.

It may have simply landed in a system still shaped for the last one.