Your Best Team Will Resist Change the Hardest

You have almost certainly heard that 70% of change initiatives fail. It gets cited in consulting decks, business books, and management training, usually with a nod toward McKinsey or Kotter.

It isn't a finding. Mark Hughes went looking for its source in the Journal of Change Management in 2011, examined the five most prominent published instances of the claim, and found that each one either stated the number with no evidence at all or cited another source that had stated it with no evidence. The trail ends at Michael Hammer and James Champy's 1993 book Reengineering the Corporation, where it appears as an explicitly "unscientific estimate." Hammer was walking it back by 1995.

I'm starting here because the myth quietly shapes how managers think about resistance. If most change fails, the implied cause is dysfunction: broken teams, weak leadership, people who don't care. That framing is comfortable, and it points you in exactly the wrong direction.

The resistance worth preparing for usually comes from your strongest team.

Why cohesion cuts both ways

A cohesive team is one where people share norms, trust each other's judgment, and have built a working rhythm together. Every one of those qualities is an asset right up until you ask them to change.

Shared norms mean there's an agreed way of doing things, so a change is a violation of something collectively held rather than a personal preference. Mutual trust means when one respected person raises a concern, everyone else weights it heavily. A working rhythm means the current state is genuinely good, so the case for disrupting it has to clear a much higher bar than it would on a struggling team.

A dysfunctional team has none of that. Nobody agrees on how things are done, so there's no consensus to violate. People are frustrated enough that almost any change looks like a possible improvement. Low cohesion means low collective resistance.

So you get the pattern that catches people out: the team you'd bet on adapts slowest, and the team you worried about goes along with it easily. The manager reads this as "my best people are being difficult" and starts pushing. That's the moment it usually goes wrong.

The resistance is doing a job

Kurt Lewin's model of change has three phases: unfreeze, change, refreeze. The step people skip is the first one.

Unfreezing means establishing, before you ask anyone to move, why the current state can't stay. Not announcing it. Establishing it, to the point where people actually feel the problem. Skip it and the change arrives as an ambush, and an ambush is a reasonable thing to resist.

When a strong team pushes back, they're usually telling you one of two things. Either you skipped the unfreeze and the case genuinely hasn't been made, or the case has been made and the change carries a real cost you haven't accounted for, one they can see from closer to the work than you are.

Both are useful. Both get destroyed if you treat the pushback as an obstacle to overcome.

What to do differently

Kotter's model puts building a coalition second, right after establishing urgency, and the sequencing matters. He doesn't say announce the vision. He says assemble enough credibility to carry it, then communicate constantly, well past the point where you're bored of hearing yourself.

On a cohesive team, that coalition can't be built from the org chart. Authority isn't what moves that group. The people whose judgment their peers already trust are what moves them, which means the practical first step is often a conversation with the person most likely to object, held early, in private, where the goal is to genuinely hear the objection rather than pre-empt it.

That conversation is slower than an announcement. It's also the difference between the 30% and the 70%.

The uncomfortable reframe

If you're about to introduce something and you expect no resistance, that's worth being suspicious about. Either your team is genuinely aligned, which is possible, or they've learned that objecting doesn't change anything, which is far more common and much more expensive.

Silence isn't consent. Sometimes it's just the sound of a team that stopped bothering.

This is drawn from the Change Management session of the curriculum I teach. The full lesson, covering Lewin, Kotter's eight steps, and what the successful 30% actually do differently, is free to read: Change Management.