Overcoming resistance to change: find what's really in the way

The problem

In the meeting, everyone agrees.

Afterwards, in the corridor, on the next call, in the quiet message to a colleague, the real conversation happens. "This will never work." "They haven't thought about what it means for us." "We tried this three years ago."

That's what resistance to change usually looks like. Not open opposition. Polite agreement in the room, and doubt everywhere else.

The instinct is to push harder: explain again, add another update, chase the people dragging their feet. It rarely works. You can't solve a problem nobody will say out loud.

The story

Years ago I sailed in the BT Global Challenge, a round-the-world yacht race. At one point our boat was leading the fleet. We were winning, so we didn't think we needed to change.

The warning signs were there. Without anyone saying it, we had become two teams within one boat. Everyone could feel it. Nobody named it. We kept trusting the approach that had brought us success, until the conditions changed underneath us.

We waited until the cost of not having the conversation was a crash.

What was in the way was never the wind or the waves. It was the conversation we didn't have.

Core Truths

Silence isn't agreement. When people don't raise concerns, it usually means they don't feel safe to, or don't believe it will make a difference.

Resistance is information. The doubts people voice outside the meeting are often the most useful data you have about where the change will fail. Treat them as early warning, not disloyalty.

If the conversation isn't happening, you have a part in that too. It's easy to decide the problem is the people who won't get on board. The shift comes when you ask what you're doing that makes it hard for them to speak.

Waiting doesn't fix it. Unspoken worries don't fade with time. They harden into stories, and the stories spread.

The argument is rarely about the thing on the table. Push-back about the new system is often about competence: "I was good at the old way." Push-back about the timeline is often about trust: "Last time, this landed on us."

"Fine" isn't aligned. A team that says everything is fine is often a team that has stopped saying what it thinks.

The conversation with yourself

Before you ask your team what's in the way, be honest about what's in yours.

• What part of this change am I privately unsure about?
• What am I avoiding saying, to my team or to the people above me?
• When people push back, what's my first reaction? Do I get curious, or do I defend?
• What might I be doing that makes it harder for people to tell me the truth?

The conversation with your team

Allow 30 minutes, in a room or on a call where nobody is rushing to the next thing.

1. Name the gap. "I don't think we've talked honestly about what's hard about this change. I'd like to."
2. Own your part. "I've probably made that harder by focusing on the plan rather than how it lands for you."
3. Ask the question. "What's one thing about this change that's harder than we're saying out loud?" If trust is low, ask people to write answers on cards first, without names, and read them out.
4. Listen without fixing. Your only job here is to understand. No defending, no solving. Play back what you hear until people agree you've got it.
5. Go one layer down. For the two or three biggest concerns, ask: "What's the worry underneath that?"
6. Agree one thing. Pick the obstacle that matters most. Agree one step to tackle it, who owns it and when you'll come back to it.

If the same conversation keeps going badly, change something about it. Have it on a walk instead of in the meeting room. Agree simple rules first: one person speaks at a time, the aim is to understand, not to win. If it gets heated, pause rather than push through.

One conversation won't clear everything. These conversations come in layers, and each one makes the next easier.

If you're not the one leading the change, you can still open this conversation. Try your manager: "Can I share something I'm hearing that I don't think is reaching you?" Often the most useful person in a change is the one willing to say what everyone else is thinking.

Depth Check

1. We haven't had it.
2. We've talked about it once or twice.
3. We've talked about it, but there's no real clarity.
4. We know what's in the way, but we haven't acted on it.
5. We named it, we acted, and it changed things.

What would it take to move one level deeper this week?

Your commitment

The one obstacle I'll bring into the open this week is:

The person or team I'll have that conversation with is:

Questions people ask

Why do people resist change?

Most resistance comes from loss, uncertainty or fear rather than stubbornness. People worry about losing status or competence, don't know what the change means for them, or don't believe it's safe to say what they think.

What is a common cause of employee resistance to change?

Not knowing what the change means for them personally. When that question goes unanswered, people fill the gap with the worst case, and doubts spread outside the meeting room.

How do you manage resistance to change?

Treat it as information, not disloyalty. Ask what's harder than people are saying out loud, let them answer anonymously if trust is low, listen without fixing, find the worry underneath, and act visibly on one thing.