Insight

Change fatigue

Change fatigue is not resistance. Resistance pushes back, and that is information. Fatigue pushes against nothing any more: it is spent resilience, built up by change after change. And because it is quiet, it is almost always seen too late.

each defensible on its own
Frame 1 · The stack

Change on top of change

Fatigue rarely comes from one big change. It comes from the stack: system, structure, manager, process. Each defensible, together unbearable.

resistance pushes back fatigue goes flat
Frame 2 · The difference

Tired is not opposed

Resistance pushes back, and that is information. Fatigue pushes against nothing any more: the line goes flat. Confuse the two and you treat exhaustion as unwillingness.

"but..." before now silence is not agreement
Frame 3 · The signal

The silence after the objections

No more pushback, but no questions either. "This will blow over too." Someone who is tired will not even invest in objecting. Silence here is not agreement.

finished, and said out loud
Frame 4 · Close things

Close what is still open

Name what earlier changes delivered, and formally close what has fizzled out. For the people it was one continuous change, so give them endings.

now later later a pause said out loud gives air
Frame 5 · Choose

What has to happen now, what can wait

Every pause you say out loud gives resilience back. Doing three changes half way at once costs more than doing one fully and honestly parking two.

the spring comes back
Frame 6 · The spring

Resilience comes back

Acknowledging the stack, visible endings, honest choices and predictability. The line that went flat springs back. Only then will a next change carry.

What this is about

Change fatigue is not resistance. Resistance pushes back, and that is information you can work with. Fatigue pushes against nothing any more. It is spent resilience, built up by change after change, often without a single one ever being visibly finished. And because fatigue is quiet, it is almost always seen too late.

How to spot it

  • The objections disappear, and so do the questions. No more pushback in the meeting, but not a single question either. Someone who is tired will not even invest in objecting.
  • Cynicism as politeness. "We’ll see" and "this will blow over too" are not provocations. They are the words of people who have learned that going along costs energy and delivers nothing.
  • Everything slows down without anyone obstructing. Deadlines slip, actions sit half done, and there is nobody to point to. The organisation is running on reserve.

Where the fatigue comes from

Rarely from one big change. Almost always from the stack: the new system, the new structure, the new manager, the new process, each defensible on its own, together unbearable. And from what was missing every time: a visible ending. Changes that quietly fizzled out without anyone saying what they had delivered. To the organisation those were closed projects. To the people it was one continuous change with no end.

What works

Acknowledge the stack first, out loud and without softening: a great deal has been asked here these past years. That acknowledgement costs nothing and opens more than any plan. Then close things visibly: name what the earlier changes delivered, and formally close what has fizzled out. Next, choose in the portfolio: what has to happen now, what can wait. Every pause you say out loud gives resilience back. And restore predictability: fatigue grows faster from uncertainty about what is still coming than from the work itself.

How we go about it

We map the change history before we start anything new: what has this organisation carried these past years, and which of it was finished? Often the first piece of change work is not starting, but closing. Read more about how we work →

When this insight helps

When a change runs slower than the resistance explains. When you want to judge how much give is left at the start of a new change. And at annual planning, when the portfolio is fuller than last year again. Change fatigue works closely with the capacity ceiling: that one is about the hours, this one about the resilience.

Is it running slower than the resistance explains?

Then the question is how much give is left. In a conversation we map the change history and the resilience.