Change fatigue, revisited: the maths hasn’t changed — but our options have
It’s a curious thing, change fatigue. It seems to be at epidemic proportions, at the very moment we are more equipped than ever to embrace continuous change. A while back Lena Ross and I pulled the topic apart in an episode of #brainpickers, and then we published a piece I wrote on it some years ago.
Rereading it, two things struck me: how little the fundamentals have shifted, and how much sharper our toolkit has become in the meantime.
Let me start where I always start. Change fatigue is best understood as a mathematical equation —the rate and volume of change is exceeding the recipient’s ability to deal with that change. That framing matters, because it explains why change fatigue is so tricky to ‘solve’ for. The maths is different for every person. The ability to absorb change is a highly personal factor, so what overwhelms one colleague barely registers for another. There is no single dial you can turn.
But here is what has changed since I first wrote that. The numerator has exploded.
The numbers have got worse
When I first described change fatigue as an equation, I was making a conceptual point. Now the data does the talking. Recent research suggests that around three-quarters of employees report moderate-to-severe change fatigue, with a sizeable chunk describing it as extreme — a dramatic increase over the last decade. The average employee is now navigating well over a dozen concurrent change initiatives at any one time, and a large proportion of those changes overlap, compete, or
quietly contradict each other.
Gartner’s 2025 research adds more colour. Only about a quarter of the workforce is embracing change quickly without damaging their health. Fewer than half of employees actually realise the change goals their organisation sets, and only around a third of business leaders report achieving healthy change adoption. Nearly four in ten leaders now name change itself as a significant source of stress for their teams. Perhaps most damning: the overwhelming majority of HR leaders don’t
believe their managers are equipped to help employees who are struggling with change fatigue. In at least one recent barrier-to-success survey, change fatigue ranked second only to sheer lack of capacity.
So the epidemic language is not hyperbole. And it sits alongside a genuine paradox — we have never had better methods, better tooling, or better evidence for how to lead change well, and yet the fatigue is deepening. That gap is the interesting bit.
The signs haven’t changed
The symptoms I described years ago hold up. Change fatigue tends to show up as a disengaged workforce, poor performance, decreased health, increased absenteeism, and — the tell-tale one — a flat refusal to acknowledge the changes being introduced at all. Individually these look like performance or attitude problems. Read together, and especially when they cluster across a team, they are the signature of a system asking people to absorb more than they can.
Because that is the shift in thinking I most want to land. Change fatigue is cumulative, and it is felt at a group and organisational level, not just an individual one. It is not, primarily, a personal-resilience deficiency to be coached away. It is a systems and leadership problem.
The causes still fall into two buckets. At an enterprise level, fatigue is rarely deliberate — it’s usually that leaders don’t communicate with each other about what they are each doing, so nobody has line of sight on the total load landing on any given team.
Fourteen initiatives feel like fourteen ambushes precisely because no single leader ever intended to launch fourteen. At an individual level, the drivers are more personal — self-esteem, the ability to assert, emotional intelligence, mindfulness — the internal resources people draw on to meet uncertainty.
What the research now tells us to do differently
Here is the finding that should reframe how we all approach this: less change management often produces better results. Organisations that rigorously govern their change portfolio — actively rejecting a meaningful share of proposed initiatives — report materially higher transformation success than those that try to run everything at once. Concentrating resources on fewer, better- supported changes beats spreading yourself across many. If you take one thing from this piece, take
that.
Which is where agile change practice earns its keep. When I wrote my original recommendations, I was reaching, instinctively, for exactly the principles that agile ways of working now give us a proper operating system for. Let me update the enterprise-level playbook through that lens.
Govern absorptive capacity like a work-in-progress limit.
My original advice was portfolio planning and scheduling, with decisions made on ‘absorptive capacity’. Agile gives that teeth. Treat concurrent change the way a good Kanban team treats work in progress — as a hard constraint, not an aspiration. If the system is full, the next change waits, or something else stops. The public change
radar I’ve always advocated for is, in agile terms, a visible backlog: people can see what’s coming and pull for detail when they’re ready, rather than having it pushed at them.
Work in smaller batches.
The single most useful move against fatigue is to favour iterative, incremental change over large, one-time transformations. Smaller increments are simply easier to absorb, cause less disruption, and give people wins along the way. Big-bang change is where fatigue goes to compound.
Establish rhythm and cadence.
This is the counter-intuitive one, and the research backs it hard: stable, predictable cadences actually increase an organisation’s capacity to adapt. Regular check-ins, forums and review sessions reduce fatigue while holding change volume steady, because predictability lowers the threat response. Rhythm is not bureaucracy — it’s how you make continuous change feel survivable.
Bundle and sense-make, anchored to purpose.
Bundle discrete changes into a common theme so they’re easy to make sense of — ten separate changes landing under one regulatory agenda is one story, not ten shocks. Then actively sense-make for people and connect the work to a clear ‘why’.
Anchoring on purpose remains one of the most reliable levers we have.
Communicate in advance — and get off email.
Communicate ahead of time to reduce the shock and give people room to process. And, as I said years ago and will keep saying: most organisations facing change fatigue are still using email as their default change-communication channel. That’s craziness. Be respectful of the audience you want to bring on a journey — there are better ways to do it.
Build change reflexes, not just change plans.
The most encouraging recent finding is that when people apply well-practised ‘change reflexes’ — openness, managing their time and attention, understanding the business context, using technology well, working with others, regulating their
emotions — they’re several times more likely to achieve healthy adoption, with markedly better wellbeing. Crucially, these are built through repeated practice in the flow of everyday work — ‘micro-moments’ — not through a one-off training day. This is capability uplift done properly: embedded in the day job, with time protected to actually do it.
And don’t forget the individual
The systemic view doesn’t let us off the hook on the human one. At the individual level, the old advice stands, and the neuroscience Lena and I keep coming back to explains why it works: build the dopamine and reduce the threat. Praise good work, acknowledge effort, say thank you to your team members. Take the time to celebrate achievements and previous changes rather than sprinting straight to the next thing. Run retrospectives — proper lessons-learned that genuinely feed forward — so people approach the next change with earned optimism rather than dread. And wherever change involves loss, make sure it’s countered with a visible gain.
There’s a growing evidence base, too, that self-leadership acts as a buffer — people who cancregulate their own attention, energy and story about the change fare better under load. That’s notcan argument for pushing responsibility back onto individuals; it’s an argument for actively building those capabilities as part of how we lead change.
Because that’s the real reframe. We’re not trying to make people endlessly resilient to a firehose. We’re trying to turn the firehose down to a rate the organisation can actually drink from — and give people the reflexes, rhythm and recognition to thrive at that pace.
Frequently asked questions
What is change fatigue?
Change fatigue is what happens when the rate and volume of change in an organisation exceeds people’s capacity to absorb it. It’s best understood as an equation — too much change, arriving too fast, for the personal resources someone has to deal with it. Because that capacity is highly individual, the same change load can exhaust one person while barely registering for another.
What are the signs of change fatigue?
Common signs include a disengaged workforce, declining performance, poorer health and wellbeing, rising absenteeism, and a refusal to acknowledge or engage with new changes. On their own these can look like ordinary performance or attitude problems; when they cluster across a team, they usually signal change fatigue building at a group level.
What causes change fatigue?
The causes are both organisational and individual. At an enterprise level it’s rarely deliberate — leaders launch competing initiatives without coordinating with each other, so the cumulative load landing on any one team goes unseen. At an individual level it’s shaped by personal factors such as self-esteem, emotional intelligence, the ability to set boundaries, and how much support a person has around them.
How do you reduce change fatigue in an organisation?
The most effective move is to reduce the volume of concurrent change by rigorously governing your change portfolio — saying no to some initiatives so the rest are properly resourced. From there: work in smaller, incremental batches; establish a predictable rhythm of communication and review; bundle related changes into a single story; communicate ahead of time; anchor everything to a clear purpose; and stop defaulting to email as your change-communication channel.
How can agile practices help with change fatigue?
Agile ways of working provide practical tools for managing change load. Treat concurrent change like a work-in-progress limit, capping how much runs at once. Deliver change iteratively, in smaller increments that are easier to absorb than a single big-bang transformation. Make the change pipeline visible as a backlog people can pull detail from when ready, and use regular retrospectives so lessons from one change genuinely improve the next.
Is change fatigue the same as burnout?
They’re related but not identical. Burnout is a broader state of chronic exhaustion from sustained stress across work; change fatigue is specifically the exhaustion, apathy and resistance that accumulate from frequent, ongoing organisational change. Left unmanaged, change fatigue is a significant contributor to burnout.
Can change fatigue be measured?
To a degree, yes. Organisations track it through engagement and pulse surveys, absenteeism and turnover data, adoption rates on recent changes, and increasingly through sentiment analysis. A simple starting point is to map how many concurrent changes are landing on each team against their realistic capacity to absorb them — the two sides of the change-fatigue equation.
