Change Saturation Is Rarely the Real Problem — Saturation is a description, not a cause

When change struggles, “saturation” is often the first explanation offered. There is simply too much going on. People are overwhelmed. The organisation needs a pause. Sometimes this is true. More often, it is a convenient diagnosis that obscures what is actually making change hard. Most organisations are not failing because they are doing too much change. They are failing because the change they are doing lacks coherence, clarity, and cumulative sense.¹

Why saturation is such a tempting explanation

“Saturation” feels neutral.² It avoids assigning responsibility. It suggests that strain is inevitable rather than designed.² It offers a simple answer to a complex problem. From a leadership perspective, it can also feel compassionate. Acknowledging overload signals awareness and concern.

But saturation is a description, not a cause. Treating it as the root problem often delays more difficult conversations about prioritisation, sequencing, and meaning.

What organisations actually experience as “too much”

When people say they are saturated, they are rarely counting initiatives. They are responding to something more subtle:

• competing narratives about what matters
• shifting priorities that invalidate yesterday’s work
• unclear trade-offs between initiatives
• repeated resets that undermine confidence
• constant cognitive switching without closure

This is not volume overload. It is coherence overload. The organisation is asking people to hold too many unfinished stories in their heads at once.³

Why reducing volume rarely fixes the problem

When saturation is diagnosed as volume, the response is predictable. Initiatives are paused. Timelines are extended. New work is deferred. Sometimes this provides temporary relief. Often, it does not address the underlying strain. If priorities remain unclear, if sequencing is incoherent, and if leaders continue to signal urgency in conflicting directions, the experience of saturation returns quickly — even with fewer initiatives. The problem was never the number of changes. It was how they were framed, connected, and led.

The cost of misdiagnosing saturation

Treating saturation as the problem carries its own risks. It can normalise disengagement. It can justify delay without improving design. It can create the impression that resistance is a capacity issue rather than a sense-making issue. Over time, it also teaches the organisation something unhelpful: that waiting is safer than committing. This erodes momentum and makes future change harder, not easier.

A more accurate way to think about capacity

Capacity is not just about time or effort. It is about how much uncertainty, ambiguity, and contradiction an organisation can hold at once.⁴ When change is coherent, people can tolerate a surprising amount of disruption. When it is not, even small changes feel exhausting. This is why organisations sometimes experience fatigue during relatively modest initiatives, and resilience during far more demanding ones. The difference is not volume. It is meaning.

Why leaders unintentionally create saturation

Most saturation is not malicious or careless. It is cumulative.

Leaders respond to external pressure. They launch initiatives with good intent. They reprioritise as conditions shift. What is often missing is deliberate closure and explicit sense-making. Without those, the organisation experiences change as a series of overlapping demands rather than a coherent direction of travel. People are not resisting change. They are trying to make sense of it.

Reframing saturation as a design issue

When saturation is reframed as a design issue rather than a volume issue, different questions emerge.

• What are we asking people to pay attention to right now?
• What can safely be deprioritised or stopped?
• Where are we creating unnecessary cognitive switching?
• What story does this change fit into?

These questions are harder than counting initiatives. They are also far more useful.

A different starting point for capacity conversations

If organisations want to address saturation meaningfully, they need to stop asking how much change is happening and start asking how well it is being made sense of. That shift moves the conversation from fatigue to focus, from overload to coherence, and from delay to deliberate choice. This is one way of thinking about why change succeeds or fails. Other pieces go deeper into how cognitive load, sequencing, and prioritisation shape adoption and performance.