5 leadership behaviors that create change resistance (and how to stop)

Which of these 5 behaviors are you doing right now? 

Change resistance isn't something that happens to your transformation. It's something you create through specific, predictable leadership behaviors.

I get at least two urgent calls a year from executives asking me to "fix" projects experiencing resistance. Sometimes we can recover. Other times, the damage is done: the resistance persists long after go-live, creating expensive reliance on workarounds, external support, and recovery efforts that could have been avoided.

Here's what I've learned after years of diagnosing why transformations fail: resistance isn't irrational. It's a predictable response to how leaders execute change. And the behaviors that create it are so common that most leaders don't even realize they're doing it.

Below are the five leadership behaviors that trigger resistance and the execution moves that prevent it.

Leadership behavior #1: Waiting too long to support people activities

Leaders delay getting help on the people side of projects, thinking they can save money or time by waiting until all decisions have been made. By the time employees are brought in, the design is locked, the timeline is set, and people are expected to adapt quickly.

This triggers loss aversion and the endowment effect—two behavioral principles that explain why people resist change even when the rational case is clear. Research by Kahneman and Tversky shows that people weigh potential losses about twice as heavily as equivalent gains. When employees are brought in late, they've already "owned" the old way of working. The new way feels like a loss, not an opportunity—and they resist accordingly.

When people feel like they don't have a choice, they push back. Not because they're irrational, but because you've designed the change process to trigger the psychological mechanisms that create resistance.

Don't wait until the solution is built to think about adoption. Map the behaviors you need people to stop doing and start doing in the first 90 days post-launch. Then work backward: What needs to be true for those behaviors to happen? What capability gaps exist? What friction points will people hit? What emotional triggers will surface?

Design your change activities into the project timeline—not as an afterthought once technical decisions are locked. Involve employees early so they co-create the solution instead of inheriting it.

Leadership behavior #2: Ignoring warning signs of resistance

Many leaders overlook early symptoms of resistance, dismissing them as "normal" friction or assuming they'll resolve on their own. The most common warning signs I see:

Ignoring these signals violates psychological safety—the belief that you won't be punished or humiliated for speaking up with concerns, questions, or mistakes. Amy Edmondson's research shows that without psychological safety, people comply publicly but resist privately. When leaders dismiss early concerns, they send a message: "Your input doesn't matter." So people stop offering it—and resistance goes underground, where it's much harder to address.

Additionally, emotions are contagious. When fear or apathy spreads through a team without being acknowledged, it compounds. What starts as individual doubt becomes collective resistance.

Don't wait for resistance to become a crisis. Build a simple diagnostic into your weekly leadership rhythm:

COM-B Framework (Capability, Opportunity, Motivation → Behavior):

Each type of resistance requires a different intervention. If you're seeing apathy, that's a motivation gap—adding more training won't fix it. If you're seeing fear, that's often a capability gap disguised as emotion—people don't believe they can succeed. If you're seeing siloed work, that's an opportunity gap—the environment isn't set up for collaboration.

Run this audit weekly. When you spot a signal, dig deeper into the underlying cause and adjust your approach.

Leaders assume that HR will manage all people-related issues without providing the necessary resources, clarity on roles, or capacity to do the work. HR professionals end up overwhelmed, under-resourced, and unable to support the change effectively. In the worst cases, HR becomes a resistor rather than an ally—because they're being asked to do the impossible.

This is diffusion of responsibility—when accountability is unclear, everyone assumes someone else is handling it, and nothing gets done. Behavior change requires role-specific accountability. Who owns ensuring that frontline managers have the skills to coach their teams through the transition? Who owns making sure the new workflow is actually easier than the old one? Who owns tracking whether key behaviors are happening?

If the answer is "HR," you've already failed. HR can support, facilitate, and advise—but they can't own behavior change for the entire organization.

Stop assigning "people stuff" to HR and start assigning specific behavior change accountabilities to the leaders closest to the work.

Create a behavior change accountability map:

Have explicit conversations with each role about what they're accountable for. And if someone doesn't have capacity, create it—don't just add "change support" on top of an already full workload.

Some leaders shy away from difficult conversations because they don't want to deal with unpleasant emotions like fear, anger, and grief. They tell themselves they aren't the "touchy-feely" types, so they avoid the conversation entirely—or delegate it to someone else.

Avoidance makes it worse. When leaders don't acknowledge fear or address concerns, confusion and uncertainty curdle into anger. And anger is much harder to work with than fear.

Here's what neuroscience tells us: emotions last about 90 seconds—unless we re-trigger them through our thoughts or actions (Jill Bolte Taylor). When someone expresses fear and you avoid the conversation, you're not making the emotion go away. You're leaving them alone with it, and they re-trigger it every time they think about the change. That 90-second wave of fear becomes sustained anxiety, which becomes resistance.

Additionally, Lisa Feldman Barrett's research shows that emotions are constructed by context. When leaders avoid difficult conversations, they create a context where people interpret the change as threatening. If you change the context—by acknowledging the fear, validating the concern, and helping people see a path forward—you change the emotional response.

You don't need to be a therapist to handle difficult conversations. You just need to stop avoiding them.

Here's the 90-second rule in practice:

The goal isn't to eliminate fear; it's to create space for the emotion without letting it escalate into sustained resistance. Doing something is almost always better than nothing.

In high-pressure situations, leaders focus on tangible tasks like negotiating contracts or finalizing technical specs while delaying or avoiding the ambiguous ones. Questions like "How will roles change?" or "What happens to my team?" get pushed to the side because leaders don't have clear answers yet.

Ambiguity creates cognitive load and uncertainty avoidance—two forces that make people default to the status quo. When people don't know what's coming, their brains fill in the gaps with worst-case scenarios. Neuroscience research shows that uncertainty activates the same threat response in the brain as physical danger. Your silence isn't neutral—it's interpreted as a threat.

The unknown and uncertainty are places that create fear and doubt for employees. And once again, if those emotions aren't addressed, they turn into anger and resistance.

You don't need to have all the answers to manage ambiguity. You just need to stop pretending you do.

Use the clarity cascade framework:

This reduces cognitive load by giving people a mental model for what's happening. It also builds trust because you're being transparent instead of pretending everything is under control.

Leaders who learn to master fear and ambiguity in themselves can help their teams do the same. And teams that work through hard things together build the capability to keep growing.

 What to do next

Leaders can make change easier by avoiding these common pitfalls that create resistance. But knowing what not to do isn't enough—you need a process for diagnosing resistance and designing the right intervention.

That's where behavioral science comes in. The COM-B framework (Capability, Opportunity, Motivation → Behavior) gives you a systematic way to identify why resistance is happening and what to do about it. Most leaders misdiagnose resistance as a motivation problem ("they just don't want to change") when it's actually a capability or opportunity problem. And that misdiagnosis leads to the wrong intervention, which makes resistance worse.

If you're leading a transformation and you're seeing early warning signs of resistance, don't wait until it becomes a crisis.

Start here: Download the COM-B Resistance Audit

A 10-minute diagnostic tool to identify whether your resistance problem is capability, opportunity, or motivation—and what to do about it.

Want to master the full spectrum of change leadership skills needed to master transformation execution?

Change resistance is just one of the challenges leaders face when executing transformation. The changecapable^TM Leadership Program equips you with the frameworks, behavioral science tools, and execution strategies to lead change that sticks. 

Learn about The changecapable^TM Leadership Program and join the waitlist for the Fall 2026 cohort to receive priority registration.