The transformation project has been running for three months. The strategy is in place, the roadmap approved, the budget released. And yet nothing happens. Or worse: the wrong things happen. Teams continue working with the old processes. Executives nod in meetings and then ignore the decisions. IT keeps finding new technical reasons for delays.
The typical reaction: break the resistance. More pressure. Clearer directives. Threaten consequences.
Resistance is not a disruption in the system. It is the system telling you something. The question is not how to overcome it. The question is what it is telling you.
A division head I accompanied through a reorganization faced exactly this problem. Her team was blocking the new processes, even though everyone had agreed in the town hall. Her first reaction was frustration: “They just don’t want to.” Her second reaction, after an honest conversation with three team leaders, was sobering: “They do want to. But our incentive systems still reward the old behavior. We moved the finish line for them but didn’t adjust the compass.” That was not refusal. That was a signal.
Not all resistance has the same cause. And not every cause requires the same response. Before you act, you must diagnose.
Not Understanding: “I don’t know what is expected of me.”
The most common and easiest to fix cause. The change was communicated but not understood. The “what” is clear, but not the “why” or the “how specifically for me.” Symptoms: passivity, questions, waiting, different interpretations in different teams. The solution is not to communicate louder but clearer. Not more often but more concretely. What does the change mean for the daily work of this specific department? Who explains it? Who answers questions? Middle management plays the crucial role here as translator.
Not Being Able: “I don’t have the skills or resources.”
The change is understood, but implementation fails due to missing competencies, tools, or time. People want to but cannot. Symptoms: frustration, overload, quality problems, workarounds. The solution is not to motivate but to enable. Training, resources, realistic timelines. Transformation on top of daily business without creating space is a recipe for failure.
Not Wanting: “I see no point, or I’m losing something.”
The most difficult category. People understand the change, could implement it, but don’t want to. Because they don’t see the point. Because they fear disadvantages. Because they don’t trust leadership. Often there is something behind it that is chronically underestimated in transformations: loss. People lose status, routines, sense of competence, sometimes colleagues. Organizational researcher William Bridges described this mechanism as the difference between “change” and “transition”: change is the external transformation, transition is the internal process of letting go, reorientation, and new beginnings. Resistance is often grief work in disguise. People are not fighting against the new. They are mourning what they are losing. Symptoms: cynicism, working to rule, emotional reactions, turnover. The solution is honest engagement. What are the actual losses? Have they been acknowledged? Loss cannot be talked away, but it can be honored.
Not Being Allowed: “The organization rewards the old behavior.”
Often overlooked: people want to and could, but structures, processes, or incentives work against the change. The system punishes the new behavior and rewards the old. You demand teamwork, but the bonus depends on individual performance. You demand speed, but every decision requires three signatures. That is not resistance. That is intelligence. Symptoms: contradictions between directive and reality, goal conflicts, defensive behavior. The solution is not to change the people but the system. Align incentives with the new goals, adjust processes, question structures.
| Source | Typical Symptoms | Solution Direction |
|---|---|---|
| Not Understanding | Passivity, different interpretations | Clearer, more concrete communication |
| Not Being Able | Frustration, workarounds, overload | Enablement, resources, realistic timelines |
| Not Wanting | Cynicism, working to rule, emotions | Dialogue, acknowledge losses, convey purpose |
| Not Being Allowed | Goal conflicts, defensive behavior, contradictions | Adjust incentives and structures |
Most transformations do not fail because of “not wanting.” They fail because of “not being able” and “not being allowed,” which were misdiagnosed as “not wanting.”
Before you respond to resistance, ask five questions.
Where exactly does the resistance occur? Local resistance (one team, one department) indicates local causes. Systemic resistance (everywhere) indicates a problem with the change itself.
Who is resisting? Is it the usual skeptics or also colleagues who normally go along? If your best employees are doubting, you have a real problem. Then your plan is wrong, not the people.
What exactly is being criticized? The goal? The path? The speed? The communication? The more precisely you understand what is being criticized, the more targeted your response can be.
What if the criticism were justified? The most painful question. Assume for a moment that the resistance is right. What would that mean? What would you have to change?
Have you listened or only informed? There is a difference between “We communicated it” and “We understood what came back.” Information is not communication. Sending is not dialogue.
When you accept resistance as information, your actions change fundamentally. You make it visible early instead of suppressing it, through spaces where honest feedback is possible. You differentiate instead of generalizing, because not understanding requires communication, not being able requires enablement, not wanting requires dialogue, and not being allowed requires structural change. Those who answer everything with “more pressure” solve only one of four causes and exacerbate the other three. You recognize patterns instead of fighting individual cases: when the same criticism comes from different corners, it is not a communication problem of individual troublemakers. And you adapt instead of pushing through, because the best strategies improve along the way.
Flexibility is not a sign of weakness. Stubbornness is not a sign of leadership strength.
An important caveat: not all resistance is justified. There is principled resistance that is blanket, unfounded, and independent of content. But only treat resistance as “principled” once you have definitively ruled out the other three causes (understanding, being able, being allowed). That is rarely the case before month six. In practice, resistance is often prematurely classified as principled when the actual causes have not yet been addressed.
The shortest path to failure is dismissing all warning signals as resistance. The most successful transformations are those in which resistance became visible early, was taken seriously, and the strategy was adjusted accordingly.
Fighting resistance feels like leadership strength. It is visible, decisive, active. Understanding resistance feels like weakness. It requires listening, reflection, possibly adapting. But transformations that take resistance seriously early and integrate it have significantly higher success rates than those that ignore or fight it.
Resistance is information. Your most valuable early warning system. The question is not whether you can turn it off. The question is whether you are smart enough to listen to it.
Tomorrow, take the transformation project that is currently stuck. Don’t ask “How do we break the resistance?” but “What is the resistance telling us?” The answer will be uncomfortable. But it will help you more than any escalation.
Middle Management in Transformation – Where resistance occurs most frequently and why middle management is the key.
The Culture You Didn’t Order – Resistance often reveals the gap between proclaimed and lived culture.
Proven tools and models for self-application are available under Solutions.
If you want to take these thoughts further for your company, a no-obligation initial conversation is worthwhile.
