A technology firm in Germany. A year of design work. Consultants, approval from the board, training delivered to every team.
Three months later: no one was using the new process.
Management had an immediate answer: resistance to change.
I had heard the same diagnosis in three other organisations that year. I asked a different question.
What is resistance to change?
Resistance to change is a real force. People protect what they know. They push back when they don't understand why something is changing, when they fear losing status or competence, or when they don't trust the people driving the change.
These concerns are legitimate. They deserve real responses: clear communication about the reasons, involvement in the design, honest answers to hard questions about what this means for people's roles.
The standard change management playbook, Prosci's ADKAR, Kotter's 8 steps, the stakeholder engagement frameworks, was built to address this. And it works, when resistance is actually the problem.
But in a significant share of failed change programmes I encounter across Europe, Asia, and the US, the problem is something else entirely.
Why the standard playbook fails
The standard playbook assumes a motivated blocker: someone who could change but won't. So it responds with persuasion, better communication, more involvement, clearer leadership.
Apply this to the wrong problem and you get a predictable result. Stronger messages land nowhere. More workshops add to the load. Leaders work harder and wonder why nothing moves.
The standard playbook is a solution to the wrong diagnosis.
I see this pattern in multinational teams as much as in local organisations. A German engineering firm running five concurrent initiatives. A financial services team in Singapore three months into a post-merger integration. A Dutch scale-up where the leadership team had changed twice in eighteen months.
In all three cases the diagnosis was resistance. In all three cases the real constraint was capacity.
It's not resistance. It's capacity.
Resistance has a direction. People are against something specific. They argue, avoid, or openly disengage from a particular change. If you removed the change, they'd feel vindicated.
Capacity shortage has no direction. People understand the change. They may even agree with it. But they have no room to absorb it. Three projects already running. A recent reorganisation still digesting. A new manager still being figured out. Daily operations with no slack.
The problem wasn't resistance. It was capacity.
If you remove the change from a team with a capacity problem, they don't feel vindicated. They feel relieved. That's the diagnostic difference.
When capacity is maxed out, behaviour becomes predictable. People ignore updates, not because they disagree, but because there is no mental room to process one more thing. Decisions slow down. Initiative drops while goodwill remains. People do what is asked and nothing more. That looks like disengagement. It's exhaustion.
Three signals that capacity is the problem
Before deploying any change management strategy, check for these three signals.
- People understand the change but behaviour doesn't shift. If the workshops were attended, the rationale is clear, and people nod when you explain it, but nothing actually changes in daily work, this is a capacity signal. Understanding doesn't equal room. You can know exactly what you should do differently and still not have the bandwidth to do it consistently.
- Initiative drops but goodwill stays. People remain polite, do what is asked, and meet their obligations. But the extra initiative, the proactive ideas, the energy for the new, stops. That's not a character flaw. It's a signal that available energy is fully consumed by existing demands.
- Decisions slow down, even simple ones. When a team is overloaded, retrieving context costs effort that would normally be automatic. Simple decisions take twice as long. Not because people are conflict-avoidant or unclear on direction, but because cognitive load is at its limit.
Resistance looks different. Resistance argues. It has a specific target. It creates friction around a particular change. Capacity shortage has no target. It's absence, not opposition.
The Capacity Check: three questions
Before I launch any change initiative, I run what I call the Capacity Check. Three questions to the leadership team.
How many change initiatives are running in parallel right now? Formal ones and informal ones. The new CRM system that's still being adopted. The team restructure from six months ago. The new performance review cycle. More than three concurrent changes is usually too many for any team to absorb without losing quality on all of them.
When did this team last fully absorb something new? Not when was the last training. When did new behaviour actually become the default? When was the last time something was launched and stuck? If the answer is "I'm not sure," that's information.
What stops when this starts? This is the hardest question. Organisations are good at starting. They are poor at stopping. Adding a new initiative without removing something creates a system where nothing gets the attention it needs. This question forces a trade-off. Most organisations skip it. That's where the overload starts.
These three questions don't take long. They change the conversation from "how do we get people on board?" to "do we have the conditions for this to work at all?"
What happened in Germany
Back to the technology firm.
We ran the Capacity Check. The result: five active change initiatives. Two reorganisations in the preceding eighteen months. A new reporting system launched four months earlier that was still generating daily friction.
We stopped two of the five initiatives. We gave the new process three months of exclusive attention. No new projects in that period.
Six months later: the process was in use across all teams. Not because resistance was overcome. Because there was finally room.
The change itself didn't change. The conditions for absorption did.
What this changes in practice
When you see resistance, you communicate better, involve more, make the case stronger.
When you see capacity shortage, you do something different. You stop first. You create room before you add something new.
That shift is harder than it sounds. Stopping something requires a conversation with the business about trade-offs. It requires admitting that the calendar is already full. It requires someone with enough authority to say: not this quarter.
But the alternative is a well-designed change programme that lands on people who have no room for it. And a diagnosis of "resistance" that sends the team through another round of communication and workshops. Which adds to the load. Which confirms the capacity problem. Which produces the behaviour that looks like resistance.
The next time a change stalls in your organisation, ask this before you adjust the strategy:
Is this resistance? Or is this capacity?
The answer changes everything you do next.