By Ritvars Mētra, Founder of ReadinessCompassThe engagement scores come back down. The comments mention exhaustion, constant change and initiative overload. Someone writes “change fatigue” in the board pack, and the organisation responds the way organisations do: resilience training, a wellbeing campaign, perhaps a manager toolkit on supporting teams through change.
Six months later the scores are worse, and the same word appears in the same slide.
The interventions were not badly designed. They were aimed at the wrong object. “Change fatigue” named a symptom, the organisation treated the symptom, and the thing producing it — the volume of change landing on those teams — carried on unchanged and, in most cases, grew.
This is not a vocabulary quibble. Which word you use decides where you look for the cause, and therefore what you spend money on.
The two things, precisely
Change saturation is a property of the system. It is the relationship between how much change is landing on a given group and how much that group can absorb. It exists whether or not anyone has yet noticed it, it is measured at portfolio and group level, and it is produced by decisions about what to approve and when. Saturation has its own signals and its own measurement approach, independent of how anyone feels.
Change fatigue is a state in people. Bernerth, Walker and Harris developed a validated change fatigue measure in Work & Stress and found it positively associated with exhaustion, with exhaustion in turn linked to lower organisational commitment and higher turnover intentions. It is felt by individuals, surfaces in surveys and conversations, and is the downstream consequence of conditions set elsewhere.
One is a cause sitting in the portfolio. The other is an effect sitting in people. Confusing them means looking for the cause inside the person experiencing the effect.
Why the distinction is structural, not semantic
Occupational psychology has a well-established framework for exactly this shape of problem, and it makes the error obvious.
The Job Demands–Resources model, set out by Demerouti, Bakker, Nachreiner and Schaufeli in the Journal of Applied Psychology, divides working conditions into job demands — the things requiring sustained effort — and job resources — autonomy, support, and the things that help people meet those demands. Prolonged excessive demand without adequate recovery drives the health-impairment process that ends in strain and burnout.
Map the two terms onto that and the picture resolves. Saturation is a job demand. Fatigue is the strain it produces.
Which exposes the flaw in the standard response. Resilience training, wellbeing programmes and manager support are resource interventions. Resources genuinely do buffer demands — that part of the theory is sound, and those programmes are not worthless. But a buffer works against a bounded demand. If the demand keeps rising because the portfolio keeps growing, you are adding finite resources against an unbounded load, and the buffer is consumed. That is why the second wellbeing campaign lands worse than the first.
The same study offers a second, sharper discriminator that is genuinely useful in diagnosis: job demands were primarily related to the exhaustion component of burnout, while a lack of job resources was primarily related to disengagement.
So the texture of what you are seeing tells you where to look:
- Exhausted but still trying — people working hard, missing things, visibly depleted, still committed to doing it properly. That points at demand. Look at the portfolio.
- Disengaged but not depleted — people with capacity who have stopped investing. That points at resources: support, autonomy, trust, whether previous change was ever finished or acknowledged.
These look similar in an engagement score and require opposite responses. Reducing the portfolio for a disengaged-but-not-exhausted team will not help, and neither will a wellbeing programme for an exhausted one.
Why leaders confuse them
The confusion is systematic rather than careless. Five mechanisms produce it, and they compound.
1. You diagnose what you instrument
Almost every organisation runs an engagement or pulse survey. Almost none runs a cross-portfolio measure of change load by receiving group.
So fatigue arrives as data, on a schedule, in a format the executive team already reads. Saturation arrives as anecdote, if at all. When one side of a causal chain is instrumented and the other is not, the instrumented side gets named as the problem — not because anyone decided that, but because it is the only side with a number attached.
2. The cheaper explanation wins
Treating fatigue is administratively easy: commission training, run a campaign, brief managers. Nobody’s initiative is cancelled and no sponsor is disappointed.
Treating saturation means stopping, deferring or resequencing something that a senior person is accountable for delivering, usually with a business case and a bonus attached. The diagnosis that requires the least organisational conflict tends to be the one that gets adopted, and it is worth being honest that this is what is happening rather than pretending it is an analytical judgement.
3. The people deciding cannot feel it
Stensaker, Meyer and Falkenberg found in their work on excessive change that perceptions of it vary significantly across organisational levels, particularly between top management and middle and lower management.
Executives experience the portfolio as a list of individually justified initiatives. Frontline teams experience the intersection of all of them, landing on one desk, on top of the day job. Nobody sees that intersection unless it has been made somebody’s job to look — the same structural blind spot as the readiness gap between executives and frontline users. Saturation is therefore invisible precisely where it is created.
4. The symptom lags the cause
Fatigue accumulates. By the time it is measurable, the portfolio decisions that caused it are two or three quarters old, made by people who may have moved on, in meetings nobody is revisiting.
The lag destroys attribution. The symptom appears in the present with no visible cause attached, which makes a present-tense explanation — this team is struggling, this manager is weak, morale is low — far more available than a historical structural one.
5. The word itself points at the person
“Fatigue” is a property of a person. “Saturation” is a property of a system. Once the first word is in the board pack, every subsequent question is about people: how are they coping, what support do they need, how do we build resilience.
Nobody asks how many changes the finance team is absorbing this quarter, because the framing has already located the problem inside the employees. Language pre-selects the intervention before anyone has analysed anything.
The test that separates them
There is a straightforward empirical check, and it needs no new survey.
Plot the symptom against change load, by group. Take your existing engagement or wellbeing data, broken down by team. Then assemble how much change each of those teams is actually absorbing — number of concurrent changes, weighted by depth and by whether previous ones ever consolidated.
- If the symptom tracks the load — heavily loaded teams are flat, lightly loaded teams are fine — you have saturation. The problem is in the portfolio and no amount of support will fix it.
- If the symptom is uniform regardless of load — lightly loaded teams are just as flat — you do not have a saturation problem. You have a leadership, trust, workload or job-design problem wearing change’s clothing.
- If it is concentrated in specific teams regardless of load, look locally: that is usually a manager, a role redesign, or a capacity concentration such as expert overload.
The load side is the part organisations claim they cannot produce. Usually they can. The per-role impact and severity data in a change impact and mitigation register is already recorded by affected role rather than by project, which makes aggregating registers across initiatives the fastest route to a load figure, with a change complexity assessment supplying the weighting so a heavy change is not counted like a light one.
This single correlation is worth more than another survey question about how people are feeling.
Differential diagnosis
| Change saturation | Change fatigue | |
|---|---|---|
| What it is | A system condition: load exceeds absorption capacity | A human state: depletion from sustained change |
| Where it lives | The portfolio and its approval decisions | Individuals and teams |
| In JD-R terms | A job demand | Strain from the health-impairment process |
| How you detect it | Change load per receiving group, weighted | Surveys, exhaustion, turnover intention |
| Who feels it least | Executives, who see initiatives not intersections | Anyone not in an affected team |
| Correct response | Sequence, gate, defer, stop something | Recovery, support, workload relief, acknowledgement |
| Wrong response | Resilience training | Assuming it will pass on its own |
| If untreated | Every initiative underperforms, including good ones | Exhaustion, lost commitment, attrition |
Usually you have both — so sequence the treatment
In practice most saturated organisations have real fatigue as well, and both need addressing. The order matters.
Reduce the demand first. Until load falls, recovery support is being applied to people whose depletion is still being actively generated. You are refilling a bucket while the hole stays open, and the visible failure of that support teaches people that leadership does not understand the problem — which costs credibility you will need later.
Then support recovery, and say plainly what changed structurally. “We have deferred two initiatives and moved a third out of your year-end” does more for fatigue than any wellbeing campaign, because it is evidence that the system responded rather than the individual being asked to absorb more.
Then keep it from recurring with a capacity gate in governance, which is the durable fix and squarely the PMO’s role in managing change saturation. Portfolios that are never pruned saturate again, which is why transformation portfolios fail when they ignore employee capacity.
There is a scale problem behind all of this worth stating plainly. 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, up from two in 2016. Very few organisations increased their absorption capacity fivefold over that period. When demand rises fivefold and capacity does not, strain is the arithmetic result — not a resilience deficit in the workforce.
The question that changes the conversation
When “change fatigue” next appears in a leadership discussion, the useful intervention is not to challenge the word. It is to ask what it is evidence of.
How much change is each of these teams absorbing right now, how much of it finished, and does the pattern of fatigue match the pattern of load?
If the answer is yes, the conversation moves from wellbeing budgets to portfolio decisions, which is where it needs to be. If the answer is no, you have learned something equally valuable: the problem is real but it is not about change volume, and you have been about to spend money on the wrong thing.
Either way, you stop treating a symptom as though it were a cause — which is the actual error, and it costs more than the training courses do.
To work through the system side in detail, see what change saturation is and how to know when you have too much, or map absorption capacity by group with the change saturation assessment. The wider set of readiness conditions is covered in the change readiness resources.