By Ritvars Mētra, Founder of ReadinessCompassThe initiative was well designed. The communications were clear. The training was available, the sponsor was visible, and the team said all the right things in the workshop.
And nothing happened.
Not resistance — something flatter than that. People were polite, agreed with the rationale, attended the sessions, and then carried on exactly as before. When you asked why, you got some version of: “We’ve got a lot on at the moment.”
That is usually not an excuse. It is a capacity statement, and it is the most commonly ignored diagnostic in change management.
What change saturation actually is
Change saturation is the point at which the volume of change an organisation is asking people to absorb exceeds their capacity to absorb it. Past that point, adding more change does not add more results. It subtracts from the changes already in flight.
The academic framing is sharper than the popular one. Stensaker, Meyer and Falkenberg, in their work on when change becomes excessive, define excessive change as occurring in two distinct situations: when an organisation pursues several seemingly unrelated and perhaps conflicting changes simultaneously, or when it introduces new changes before previous changes have been completed.
Those are two different problems and they need different fixes. The first is a volume problem — too much at once, competing for the same attention. The second is a sequencing problem — each change interrupted before it consolidated, so the organisation accumulates half-adopted processes rather than finished ones.
Most organisations diagnose only the first and then try to solve it by prioritising harder, which does nothing about the second.
Saturation is not the same as change fatigue
These two terms are used interchangeably and should not be.
Saturation is an organisational condition — a measurable relationship between how much change is landing on a group and how much that group can absorb. Fatigue is the human consequence of living inside that condition.
The distinction matters because it tells you where to intervene. Fatigue is real and measurable in its own right: Bernerth, Walker and Harris developed a validated change fatigue scale in Work & Stress and found change fatigue positively associated with exhaustion, with exhaustion in turn linked to lower organisational commitment and higher turnover intentions. But you do not fix fatigue with wellbeing initiatives while the saturation that causes it continues. That is treating the symptom and adding another initiative to the pile.
Saturation is a portfolio problem. Fatigue is what it does to people.
Why this got worse
The volume genuinely increased. Writing in Harvard Business Review, Gartner’s Cian O Morain and Peter Aykens reported that in 2022 the average employee experienced ten planned enterprise changes — restructures, culture programmes, legacy system replacements — up from two in 2016.
Ten a year is roughly one significant change every five weeks, landing on people who also have a day job. Very few organisations increased their change capacity fivefold over the same period.
Prosci has benchmarked change saturation since 2007, and the share of respondents reporting their organisation is near, at, or past the point of saturation has climbed from around 59% in the earliest study to roughly three-quarters in recent waves. Saturation is now the normal condition, not the exception — which means assuming you have spare absorption capacity is the less safe assumption.
How to know: nine signals
Saturation rarely announces itself. Nobody sends an email saying the organisation is full. It shows up as a set of symptoms that are usually attributed to something else — poor communication, weak leadership, resistant culture.
Delivery signals
- Dates slip for availability reasons, not technical ones. Milestones move because the business could not free people, repeatedly, across unrelated projects.
- The same names appear on every initiative. A handful of people are the nominated expert, super-user or workshop attendee for four programmes at once — the pattern behind expert overload.
- Nobody can list what is live. Ask what changes a specific team is currently absorbing. If it takes a week to assemble the answer, or different functions give different lists, saturation is unmanaged by definition.
Adoption signals
- Adoption plateaus early and low. Usage climbs to a compliance minimum and stops. People do the smallest version of the change that avoids attention.
- Old workarounds never close. Nobody has capacity to retire the old way, so both run in parallel indefinitely — the mechanism that keeps spreadsheets running processes a new system was supposed to own.
- Training attendance falls while satisfaction scores stay fine. People are not hostile; they are triaging their calendar.
Behavioural signals
This is where the research is most useful. Stensaker and colleagues identified three ways people cope with excessive change: active engagement, passive acceptance, and detrimental responses including cynicism and the resigned “here it comes again” posture the literature labels BOHICA.
- Passive acceptance is the signal most often misread as success. Nobody objects. Nobody escalates. Nobody changes. A programme reporting “no significant resistance” in a saturated organisation is usually reporting that people have stopped bothering to argue.
- Waiting behaviour. Teams openly delay adopting, on the reasonable historical evidence that the initiative may be superseded before anyone checks.
- Middle managers absorbing rather than translating. Managers quietly shield their teams by not cascading, buffering the change instead of leading it — which removes the reinforcement that adoption depends on.
Read together, these are the difference between an organisation that disagrees with you and one that has simply run out of room. The responses look similar from a steering committee. They require opposite interventions: the first needs a better case for change, the second needs less change.
The perception gap that hides it
Here is the finding that explains why saturation persists in organisations that are actively trying to manage it.
Stensaker and colleagues found that perceptions of excessive change vary significantly across organisational levels — particularly between top management and middle and lower management. Executives systematically perceive less saturation than the people below them.
This is not executive negligence. It is structural. Leaders see the portfolio as a set of initiatives, each individually justified and individually reasonable. Frontline teams do not experience a portfolio; they experience the intersection — whatever lands on their desk, from all initiatives at once, on top of the operational day job. Nobody is looking at that intersection unless someone has been given the job of looking at it.
Two practical consequences. First, an executive-level survey will under-report saturation, reliably. If your evidence is a leadership pulse check, it is measuring the group least exposed to the condition. This is the same structural blind spot as the wider readiness gap between executives and frontline users.
Second, saturation is invisible at the level where it is created. The decisions that cause it — approving one more initiative, pulling a date forward — are taken exactly where it cannot be felt.
Measuring it properly
Counting initiatives is the wrong measure, and it is the one most portfolio dashboards use. Twelve initiatives touching twelve different teams is a manageable portfolio. Four initiatives all landing on the finance team in the same quarter is a saturated one.
Measure by receiving group, not by initiative. For each team or role, assemble:
- Concurrent changes landing on them in the period.
- Depth of each change for that group — a new report is not a new operating model. Weight accordingly.
- Timing clustering, and whether it collides with their operational peak. Four changes for the finance team in January is a different proposition from four in June.
- Residual load from previous changes not yet consolidated — the sequencing half of the definition, and the part everyone omits.
- Operational headroom: vacancies, seasonal peaks, known pressure.
Most of this already exists in your programmes, scattered. The per-role impact and severity data in a change impact and mitigation register is the natural raw material, because it is already recorded by affected role rather than by project. Aggregating those registers across initiatives is the fastest route to a saturation heat map, and a change complexity assessment gives you the weighting so that a heavy change is not counted the same as a light one.
If you want a structured starting point rather than building it from scratch, the change saturation assessment works through absorption capacity by group.
The signals at a glance
| Signal | Commonly blamed on | What it usually means |
|---|---|---|
| Dates slip for availability, repeatedly | Poor planning | Absorption capacity is already committed |
| Same people on every initiative | Key-person dependency | Capacity concentrated in too few people |
| Nobody can list what a team is absorbing | Reporting gap | Saturation is not being managed at all |
| Adoption plateaus at compliance minimum | Weak engagement | People are rationing effort across changes |
| Old workarounds never close | Resistance | No capacity to retire the old way |
| “No significant resistance” reported | Success | Passive acceptance; people stopped arguing |
| Teams visibly waiting it out | Cynicism | Learned behaviour from superseded initiatives |
| Managers buffering, not cascading | Weak management | Managers protecting exhausted teams |
| Executives report no saturation | Reassurance | Measured at the level least exposed to it |
What to do about it
Saturation is solved by subtraction and sequencing, not by better communication. Four moves, in rough order of difficulty.
Make the load visible by receiving group. A heat map by team, refreshed quarterly, changes portfolio conversations more than any argument will. It converts “people are struggling” into “the finance team is absorbing four heavy changes in the quarter that contains year-end,” which is a statement an executive committee can act on.
Sequence deliberately, and protect consolidation windows. The sequencing half of the definition means leaving deliberate gaps after a change so it can consolidate before the next one lands. A gap is not slack; it is what converts an implemented change into an adopted one.
Put a capacity gate in governance. New initiatives should have to answer “which groups absorb this, what else is landing on them, and what moves to make room?” before approval. This is squarely the PMO’s role in managing change saturation, because it is the only function positioned to see across initiatives.
Stop something. The hardest and most effective move. Organisations start initiatives far more readily than they close them, and a portfolio nobody prunes will saturate regardless of how well each individual change is run — which is why transformation portfolios fail when they ignore employee capacity. Stopping or deferring one initiative usually rescues three.
The question worth asking
When the next initiative underperforms, the standard diagnosis is that the case for change was not compelling enough, the communication was not clear enough, or the culture is resistant.
Before accepting any of those, ask a different one: how many other changes is this group absorbing right now, and how many of them finished?
If nobody can answer, that is the finding. An organisation that cannot say how much change a given team is carrying is not managing saturation — it is discovering it, one underperforming initiative at a time, and usually blaming the people absorbing it.
Change capacity is a real, finite resource. It is the only one most transformation portfolios still spend without measuring.
Saturation is one of several conditions that determine whether a change lands at all. Explore the change readiness resources to see how capacity, leadership alignment and adoption evidence fit together, or start with the AI-assisted diagnostic toolkit.