There’s a moment most tech leaders recognise. You’re in a steering meeting, someone says, “We need another wave,” and the room goes a bit… flat. Not angry. Not resistant. Just tired.
That’s the new problem.
For years, the hard part was getting buy-in for change. Now change is everywhere. Cloud moves, security uplift, data modernisation, ERP refresh, GenAI pilots, process redesign, operating model tweaks, cost programmes in the background, and a new collaboration tool someone swears will “fix” productivity. Meanwhile, the business still wants faster delivery, lower risk, and fewer incidents. With the same headcount.
So when leaders talk about the biggest barrier, it’s no longer a lack of vision or even funding. It’s the human battery. The organisation’s capacity to absorb change without quietly breaking. Therefore, leaders are increasingly confronted with “transformation fatigue”, a phenomenon where the constant demand for change overwhelms teams and hinders productivity.
And the numbers are starting to look awkward.
Gartner’s annual survey said only 48% of enterprise digital initiatives meet or exceed their business outcome targets, while a “Digital Vanguard” group performs far better. That gap matters, since it tells you what many teams already feel: plenty of activity, uneven outcomes.
At the same time, Microsoft’s Work Trend Index work points to an “infinite workday” pattern, meetings after 8 p.m. up 16% year on year, with work stretching into evenings as cross-time zone work grows.
If you’re wondering why people don’t feel fresh for “Phase 4”, that’s a clue.
The funny thing is… leaders aren’t wrong
Here’s the thing: most CIOs and CTOs aren’t pushing change for fun. They’re responding to real pressure, competition, regulation, cyber risk, customer expectations, board scrutiny, and now AI-driven urgency.
Even in Emergn’s research, employees recognise the need for change, yet more than half said they’d considered leaving based on how change is being carried out. The point isn’t “don’t change”. The point is “change that lands”.
That tension, we must change versus we can’t take much more – is the heart of transformation fatigue.
What fatigue looks like on a Tuesday
Fatigue isn’t always dramatic. It’s often practical.
– People stop reading comms. Not in protest. They just can’t process another “exciting update”.
– Teams go quiet in workshops. Not since they’re disengaged; they’re trying to survive the week.
– You get “soft sabotage”: delays, missed actions, slow adoption, half-used features.
– The same risks keep turning up: unclear ownership, poor data quality, training gaps, and too many dependencies.
One of the clearest causes is also the least glamorous: training and day-to-day support.
A 2025 Adaptavist report on technostress found 64% of knowledge workers say workplace tech has negatively impacted their lives in the last year, with 43% saying too many notifications or too many platforms cause stress and anxiety.
That’s not a “change management” buzzword problem. That’s a lived experience problem.
And it explains why “tool rationalisation” suddenly shows up on roadmaps again, not since leaders love cutting software, but since people can’t juggle ten dashboards and still do deep work.
When pilots breed cynicism
Let me explain the new pattern a lot of leaders are stuck in:
a. Launch pilots fast (often with real excitement).
b. Hit messy reality: data issues, unclear scope, process gaps, security review delays.
c. Pilot stalls.
d. Everyone moves on to the next pilot.
IDC reported that organisations in Asia Pacific ran an average of 24 GenAI pilots over 12 months, yet only 3 progressed into production, with lack of clear direction noted as a factor.
Now picture being on the receiving end of that. You attend demos, try new prompts, fill out surveys, join training, update your process, then… nothing. Next month, a new pilot appears with a new sponsor and a new slogan.
Eventually people learn a coping skill: wait it out.
That’s fatigue turning into organisational muscle memory.
The uncomfortable maths of change
There’s an old line that still stings: “When 70 percent of transformations fail…” McKinsey has made that point in its transformation commentary for years.
Leaders often hear that and think, “We need a better programme.”
Teams hear it and think, “So we’re about to spend two years on something that might not stick.”
Now add Gartner’s 48% outcome figure on digital initiatives.
Now add longer working hours and more after-hours meetings.
You can see the loop:
– outcomes fall short
– leaders push harder
– the organisation gets noisier
– adoption drops
– outcomes fall short again
It’s not laziness. It’s load.
The real villain: change saturation
Prosci uses the term change saturation for the moment when disruptive changes exceed an organisation’s capacity to adopt them, and that’s when change fatigue shows up, apathy, anxiety, burnout.
Honestly, that framing helps. It shifts the conversation away from “people are resistant” and towards “people are overloaded”.
Once you accept that, the leadership job changes. It’s less about selling change harder. It’s more about sequencing, choice, and stopping work.
“So what do we do?” Start with one awkward rule
If you want a practical reset, try this: no new major change goes live without an explicit stop decision.
Not a vague “we’ll absorb it”. A real stop. Pause, cancel, or delay something else. Put it in writing. Let the PMO (or portfolio function) police it.
This is where many organisations flinch. Stopping work feels like defeat. It isn’t. It’s governance.
And it’s linked to outcomes. Gartner’s data on “Digital Vanguard” performance hints at what mature groups do differently: clearer ownership across CIOs and business leaders, tighter focus, and fewer orphan initiatives.
Make the workday less chaotic, not more “efficient”
Microsoft’s Work Trend Index material talks about work becoming chaotic and fragmented, with longer days and more after-hours meetings in many environments.
If your transformation plan adds more meetings, more reporting, and more channels, you’re pouring sand into the gears.
Some simple shifts help more than grand speeches:
– Meeting rules that protect build time (quiet mornings, no-meeting blocks, fewer recurring calls)
– One change calendar that the whole firm can see (IT, HR, Ops, Finance — all of it)
– Less broadcast, more context: why this matters to a specific team, this month
– Short training loops close to go-live, plus floor support after launch
That last one is not optional. Training is often the first budget line to get squeezed, then everyone acts surprised when adoption is weak.
The “people manager” bottleneck no one wants to talk about
A lot of leaders assume comms is a central function issue. Yet day-to-day acceptance of change sits with line managers.
Gallagher’s 2025 Employee Communications Report flagged barriers like low capacity (49%), change fatigue (44%), and ineffective manager communication (41%).
That’s a fairly blunt message: managers are overloaded and often under-equipped, then asked to be the face of change.
If your programme plan doesn’t include manager enablement, scripts, FAQs, time, coaching – you’re hoping for miracles.
A small contradiction: standardise less, decide faster
Most transformation plans push standardisation. It makes sense. Less variation, fewer systems, fewer support paths.
Yet standardising everything at once can raise fatigue. It removes autonomy and adds friction.
So here’s the twist: standardise the decisions, not the experience.
– Standard decision rights: who owns scope, data, risk, and adoption
– Standard scorecards: what “good” looks like (outcomes, not activity)
– Standard change gating: when you stop, when you slow, when you scale
Then give teams room in how they adopt, as long as they meet the outcome. That balance lowers resistance without turning the place into chaos.
Where AI helps, and where it makes things worse
AI is a strange character in this story.
On one hand, it can remove grind: summarising calls, drafting first versions, triaging tickets, searching knowledge bases, writing test cases, speeding analysis. Used well, it gives time back.
On the other hand, AI programmes often arrive as another layer: another tool, another policy, another pilot, another training session, another “champion network”.
Emergn’s findings reported that AI initiatives were accelerating fatigue for many respondents (as picked up in industry coverage).
So the AI question becomes: are we removing work, or adding work?
If the first visible impact of AI is more admin, you’ve lost the room.
A calmer playbook that still gets results
This part isn’t glamorous, yet it works.
-
- Name the load. Put change saturation on the exec agenda, not as HR mood music but as delivery risk. Prosci’s framing helps here.
- Run fewer bets, finish more. Pilot counts are not a success metric. Production outcomes are. IDC’s pilot-to-production gap is a warning sign.
- Make ownership obvious. If it’s everyone’s job, it’s nobody’s job. Gartner’s “Digital Vanguard” point reinforces the role of shared CIO/CxO ownership.
- Treat attention as a limited resource. Tool sprawl and notification overload are not personal weaknesses; they’re system design problems.
- Stop work on purpose. Visible stop decisions build trust. People start believing change has a shape, not an endless treadmill.
And yes, keep some humanity in it. People can cope with hard work. They struggle with meaningless work.
The closing truth (and it’s a bit uncomfortable)
Transformation fatigue is not a “soft” issue. It’s a performance issue.
When people are stretched, adoption suffers. When adoption suffers, outcomes drop. When outcomes drop, leaders push harder. And round we go.
The good news is that fatigue isn’t permanent. It’s responsive. When leaders reduce noise, sequence change, protect capacity, and show they can finish what they start, energy returns. Slowly at first, then all at once.
You know what? That’s when transformation stops feeling like a storm and starts feeling like progress again.
Free Newsletter
Stay in touch. Subscribe to my free LinkedIn newsletter on strategy, technology and delivery. Read less. Know more. https://tinyurl.com/3bcbee2z