Leading change when your team resists (without forcing it)

I once announced a change in a Monday standup, felt rather pleased with my slides, and then watched the room go quiet in that specific way a room goes quiet when nobody agrees with you. One person folded their arms. Another asked a question that wasn’t really a question. By Friday the new process was technically “live” and nobody was using it.

For years I read that scene as defiance. They don’t get it. They’re stuck. They’re being difficult. So I did what frustrated leaders do — I argued harder. More logic, more benefits, more slides. It never worked, because I was answering a question nobody had asked.

Here’s what took me an embarrassingly long time to learn: resistance is almost never defiance. It’s an unmet need that hasn’t found better words yet.

The argument you keep winning isn’t the real one

When I face pushback now, I try to remember that the loud objection on the surface is rarely the actual one. In the book I describe digging into resistance like peeling an onion — the visible layer is “this won’t work,” but underneath sit the layers that actually drive the behaviour: fear of the unknown, a quiet worry about job security, a perceived loss of control, or simply a bad experience with the last change that someone promised would be great.

You cannot out-argue any of those with a deck. A person who is afraid of losing status doesn’t need your ROI projection. A person who got burned by the last reorg doesn’t need your enthusiasm — they need evidence that this time is different.

When someone resists your change, they’re not rejecting the destination. They’re telling you something about the rung they’re standing on right now.

So the job stops being how do I convince them? and becomes what does this person actually need that the change is threatening? That’s a far more useful question, because it has an answer.

Locate the rung, don’t win the argument

I think of resistance as a ladder of unmet needs, and most pushback lives on one of these rungs:

• Safety. “Will I still have a job / my standing / my expertise after this?” Loss of security and loss of control are the two heaviest stones people carry into a change.
• Clarity. “I genuinely don’t understand what I’m supposed to do differently on Monday morning.” Confusion looks identical to resistance from the outside, but it’s a completely different problem.
• Competence. “I was good at the old way. I’ll be a beginner again, in public.” Nobody wants to feel incompetent in front of people they lead or report to.
• Trust. “We were promised something last time and it didn’t land.” Past bad experience with change is one of the most under-diagnosed roots of resistance, and the most reasonable.

Notice that not one of these is fixed by a better argument. Each is fixed by a different action — reassurance, a clearer map, training and air-cover to be bad at something for a while, or simply naming the broken promise out loud before they have to.

The skill isn’t persuasion. It’s diagnosis. Keep asking a gentle “why” until the loud objection gives way to the quiet one. Usually two or three “whys” deep, the real rung appears — and it’s almost always more human and more legitimate than “they’re being difficult.”

Walk them along the arc from effort to effortless

This is where the spine of everything I write about comes in. A change doesn’t stick because you mandated it; it sticks when the new behaviour stops costing willpower and becomes the default. I think of that journey as an arc with four stages — Discomfort, Focus, Resilience, Mastery — and the leader’s job is to help a team move along it, not to skip it.

• Discomfort. Every real change begins by asking people to step into the hard new thing. This is the moment the room goes quiet. Don’t pretend the discomfort isn’t there — name it. “This will be clumsy for a while” is more honest, and more reassuring, than “this will be easy.”
• Focus. People have limited energy, and a change that asks them to alter twenty things at once dies on contact. Aim that energy at the few things that actually matter this week. Strip the new process down to the one or two behaviours that move the needle, and let the rest wait.
• Resilience. Then comes the valley — the stretch where effort is high and the reward hasn’t arrived yet. This is where most initiatives quietly die, because people drift back to the old way that still pays off faster. Your job here isn’t pressure; it’s to be the bridge across the valley.
• Mastery. Eventually repetition does its work. The new way stops needing a reminder, a login prompt, a nudge. It becomes “just how we do things” — identity, not effort.

Here’s the part I keep relearning: the goal of all that discipline is to make itself unnecessary. You’re not trying to enforce a behaviour forever. You’re pushing only until the behaviour becomes the easy default — and then you can take your hands off it.

So before you push, turn that arc into design questions:

1. Where’s the friction? Every extra click, approval, or “we’ll figure that out later” is a tax you’re charging people during the Discomfort stage — and it makes Mastery further away, not closer.
2. When does the payoff arrive? If the win is a quarter away, the Resilience valley is too long to survive. Borrow a payoff from this week — a visible early result, a small win you celebrate out loud, a peer who says “actually, this is better.”
3. Who feels the cost first? Often the people resisting loudest are paying the highest switching cost. Cut their cost first and you’ve turned a blocker into your best advocate.

If, on a Tuesday afternoon under deadline, the old way is still faster and more familiar, resistance isn’t a character flaw. It’s rational. People are choosing the option that costs less effort, and you’re labelling the result an attitude problem.

The bridge you build, then put down

There is an honest valley here, and I won’t pretend otherwise. For a while the new way is harder — people are paying the cost before the design pays them back. Your job in that stretch isn’t to crank up the pressure. It’s to be the bridge across the Resilience valley: clear communication, real support, and the patience to let people be temporarily worse at something on the way to being better.

I’ve found a few things actually move people across, and none of them are arguments. Involve them in the how before you’ve decided everything — people defend what they help build. Name the fears out loud before they have to. Find your early adopters — usually your curious, slightly restless people — and let their experience do the convincing you can’t. And celebrate the small wins loudly, because momentum is a real force; a ball that’s rolling is far easier to keep rolling than one you’re shoving from a standstill.

If you want the trackers and survey templates I use to actually surface what people are resisting — instead of guessing — they’re in the resources, and you can read more about why I care about this stuff on the about page.

But the core of it is simple, and it cost me a lot of bad Mondays to learn. Stop trying to win the argument. The argument was never the problem. Find the rung the person is standing on, walk them from discomfort toward the day the new way is the effortless one, and most of the resistance you were bracing to fight quietly stops needing to exist.