People, process, delivery and AI. Fixed properly, and measured.

Blog / Change · 2 min read

Change fatigue: when your team has had enough

One change is manageable. Five at once, with no end in sight, wears people out. How to spot change fatigue early and protect your team from it.

Published

26 October 2026

In the model

People · Energy

The symptom

Another reorg, another new tool, another "exciting new way of working". The team nods, says the right things, and changes nothing. Your strongest people seem flat. Someone you thought would never leave hands in their notice.

What's really going on

Every change costs energy: learning, unlearning, uncertainty. People can carry a lot, but not without limit. When changes overlap with no gap between them, people stop investing in any of them. They conclude, reasonably, that this one will be replaced too.

Change fatigue isn't resistance. It's a sensible response to being asked to start again too often.

Signs to watch for

  • Cynical humour: "What are we calling it this quarter?"
  • Compliance without commitment: forms filled in, behaviour unchanged
  • Good people going quiet in meetings they used to drive
  • More sickness, more mistakes, more "I'll do it later"

What to do

  1. Count the changes. List every change your team is absorbing right now, big and small. Most managers undercount by half.
  2. Shield what you can. Not every change from above needs to land at once. Stage them, and say no to the ones that can wait.
  3. Finish things. Close changes off properly: say what's done, what stays, and that this one is over. An unfinished change is still a cost.
  4. Protect some stability. Name the things that won't change this quarter: the team, the rota, the core way of working. People need something fixed to stand on.
  5. Ask before adding. Before your own next improvement, ask the team: "Have we got room for this right now?" Believe the answer.

What to say

To your own manager, when your team is at capacity:

"My team is absorbing four changes at once. They're coping, but the cost is showing: two people are flat and mistakes are up. Can we stage the next one until the system migration settles? I'd rather land one well than four badly."

Try this week

Write down every change your team is going through. Show it to them and ask which one hurts most.

Think about it

What in your team hasn't changed in the last year, and is that a problem or a relief?