Is your change initiative treating resistance as a problem to solve?
A better way is to use it as a diagnostic signal.
When employees avoid new systems, delay implementation, or show minimal effort, they’re telling you something important about the system, the context, or their unmet needs.
The real question isn’t, how do we overcome resistance?.. instead, it should be:
What does this resistance tell us about the gaps in how we are approaching our change?
I’ve identified 15 drivers that seem to keep coming up in change projects:
• Autonomy Threat • Uncertainty & Ambiguity • Identity & Status Threat • Competence Concerns • Social Disconnection • Norms Misalignment • Fairness • Ripple Effects • Past Grievances • Increased Workload • Real Harm Risk • Influence / Messenger Effects • Lack of Feedback Loops • Emotion Regulation • Leadership Trust
When you understand which drivers are active in your system, you can target strategies that work with human motivation instead of against it.
Resistance is never apperars randomly, it’s actually data.
The work is to systematically diagnose it, get to the root cause, and act with a solid hypothesis.
Most leadership teams recognize these patterns, yet few have a systematic way to diagnose which drivers are active in their context or how to address them, which is what I help teams do through behavioral diagnostics and targeted strategies.
Which of these drivers shows up most in your change work?
