The Change Fatigue Nobody Puts on the Roadmap
Why transformation fatigue is real and how to sequence change so your team can actually keep up.
Things move so quickly today that it's hard to keep up, and I say that as someone whose job is helping companies change. If I feel it, I know the people inside the companies we work with feel it more. Most of them aren't resisting change. They're tired of it arriving all at once.
There's a name for this now, and the numbers behind it are hard to ignore.
The fatigue is real
In a recent Emergn study of 751 large organizations, 82% said transformation is necessary to stay competitive. In the same study, half reported transformation fatigue, and 44% said change is coming too often. Nearly a third of employees said they feel uninformed about what their company's transformation is even for, up from a quarter the year before.
Emergn's CEO said something I keep coming back to: "Transformation fatigue isn't burnout; it's when teams stop adapting."
That's the part that worries me. Burned-out people eventually rest. Teams that stop adapting go through the motions. They attend the training and nod along but keep doing the job the old way because the old way is the one thing that hasn't changed on them this quarter.
AI poured fuel on it
More than half of the leaders in that study said AI initiatives are making the fatigue worse. That tracks with what I see. Most companies were already in the middle of an initiative when AI arrived, and AI didn't replace any of that load. It landed on top of it, with a board asking why it wasn't moving faster.
The people absorbing most of it are managers. Gallup's latest global workplace report found that manager engagement has dropped so far that managers are no longer more engaged than the people they lead. They're the ones translating every new initiative for their teams, and they're running out of gas.
The problem is collision
People can handle a lot of change. What they can't handle is five changes at once with no clear order. KPMG found that nearly half of organizations are running multiple major transformation programs at the same time. Each one has its own sponsor, its own timeline, its own training, and its own definition of urgency. Nobody owns how they land or how they fit together.
From the inside, that doesn't feel like transformation. It feels like chaos.
What actually helps
Slowing down isn't realistic for most companies. Changing in the right order is.
Start by sequencing. Some changes sit underneath others, so decide what has to land first, let it take root, and tell people what's coming next, when, and why. Knowing the order is half the relief.
Then build each change around real jobs. People adopt change when they understand the why, feel part of it, and can see their own day in it. Generic training rarely does that. Give your people the desire, knowledge, and ability to change, then reinforce it consistently and transparently.
Every change should also come with something people get to stop doing. If the new system only adds steps, your team will treat it as one more thing, and they'll be right.
And protect your managers. Give them context before their teams get it and fewer initiatives to translate at once.
What it looks like in practice
One of my favorite examples is a defense drone manufacturer we worked with. They needed a lot to change: their quality system, their DoD documentation, their product data, a new ERP, and the ability to deliver on government contracts. Trying to do it all at once would have buried any team. So we went in phases. The quality system foundation came first because everything else depended on it. Then the DoD documentation. Then the full transformation.
They earned AS9100D certification on their first attempt because their documentation reflected how the work is actually done, built around what each role does every day. And their change order cycle time dropped from 10 days to 5.
They got there by moving in order, at a pace their people could actually keep up with.
The pace isn't slowing
If anything, AI guarantees it won't. So the real advantage now is a team that can absorb change without breaking, and that gets built one change at a time, in the right order.
And if you're feeling the pace yourself, pay attention to that. Your people are probably feeling it more.
Trisha Griffis is the founder and CEO of Jer-nee, an operational execution partner that builds operational infrastructure for aerospace, defense, and manufacturing companies scaling into delivery.
