Every leader of a significant change eventually meets resistance from people they respect. Not the usual skeptics, but the reliable ones: the experienced analyst, the respected team lead, the person who always delivers. The change makes sense on paper. The business case is solid. And yet these people slow down, ask the same questions again, or quietly keep doing things the old way.
It is tempting to treat that as a communication problem ("they don't understand yet") or an attitude problem ("they don't want to change"). Sometimes it is. More often, in my experience, it is something more specific, and more useful.
On one transformation, the strongest pushback came from the analyst everyone relied on for answers. In every meeting, she raised another objection. I first read it as resistance. It turned out she was the only person who understood the exceptions the new process could not handle. Her objections were the best testing we had.
My view on this comes from two directions. As a Prosci-certified change practitioner, I have learned to treat resistance as information about where people are stuck. As a certified leadership coach, I have learned to ask before telling. Together, they point to five reasons good people resist good changes.
1 They lose something you can't see
A strong performer who suddenly seems reluctant or defensive.
What may be underneath. A change can be good for the organization and still cost an individual something real. Expertise is the most common loss. Someone who has been the go-to expert on the old process for years becomes a beginner on the new one overnight. Status, autonomy, a trusted way of working, or relationships with a team can also be at stake.
Name the loss openly instead of pretending it does not exist. Give experienced people a visible role in shaping the new way of working, so their expertise transfers rather than disappears.
On one program, a senior analyst had been the reference on the old reporting process for more than ten years. Once we asked them to co-design the new workflow and coach their colleagues through it, their objections turned into some of the most useful design input we received, and the team followed their lead.
2 They have seen this movie before
Polite agreement in meetings, and very little actual movement.
What may be underneath. Skepticism is often learned. If people have watched previous initiatives launch with fanfare and fade within a year, waiting it out is a rational strategy. They are not resisting your change. They are protecting themselves from the next abandoned one.
Acknowledge the history directly. Then make commitments small enough to keep and visible enough to notice. Trust in a change is rebuilt the same way trust in a person is: by doing what you said you would do, repeatedly.
3 They know something you don't
Objections that sound like detail, edge cases, or "that won't work here."
What may be underneath. The people closest to the work often see problems that are invisible from a steering committee. Their objection may be pointing at a real gap in the design: an exception that happens every week, a regulatory constraint, a dependency nobody mapped. Sometimes the resistance is simply right.
Treat objections as free testing. Ask people to walk you through the case they are worried about. If they have found a flaw, fixing it early is far cheaper than discovering it after go-live, and it turns critics into co-designers.
On one rollout, a team lead kept saying the new intake process would not work for their group. When we finally sat down together, they walked us through an exception that came up every week and represented a large share of their volume. Fixing it before go-live spared everyone a painful first month.
4 They don't have the capacity
Missed training sessions, half-adopted tools, and people who seem to be "not prioritizing" the change.
What may be underneath. Most changes are added on top of a full job. Nothing comes off the plate. Learning a new process while delivering on the old one, with the same deadlines, is not a motivation problem. It is an arithmetic problem.
Decide explicitly what people can stop doing, defer, or do less of during the transition. Plan for a temporary dip in productivity instead of acting surprised by it.
5 The system still rewards the old way
People who agree with the change, attend the training, and then drift back to old habits.
What may be underneath. People respond to what is measured, recognized, and asked about. If performance reviews, reports, and managers' questions still reward the old behavior, the change is asking people to work against their own incentives. Many changes fade not because people rejected them, but because nothing reinforced them.
Check what managers ask about in their weekly meetings, what gets reported upward, and what gets recognized. Align those with the new way of working, and keep reinforcing it after launch, when attention usually moves on.
What doesn't work
Some common responses tend to make resistance worse:
- Communicating more, louder. If the issue is loss, history, missing knowledge, capacity, or incentives, another town hall will not address it.
- Labeling people as resistors. It turns information into a conflict, and it teaches everyone else to keep their concerns to themselves.
- Going around them. Bypassing respected people may speed things up briefly, but it usually costs the credibility the change needs to last.
The leader's role
Most of what helps is not the change team's job alone. People look to their own leaders, and especially their direct manager, to decide whether a change is real. A visible sponsor who explains why the change matters, listens to concerns, and removes obstacles does more than any communication plan.
Coaching has taught me that the most useful move is often a question rather than an answer:
"What would have to be true for this to work for you?"
The answer is rarely what you expect, and it is almost always useful.
A quick reference
| What you see | What may be underneath | What tends to help |
|---|---|---|
| Strong performers turning defensive | Loss of expertise, status, or autonomy | Name the loss; give them a role in the design |
| Agreement without movement | Experience with abandoned initiatives | Small, visible commitments that are kept |
| "That won't work here" | A real gap in the design | Treat objections as free testing |
| Missed training, partial adoption | No capacity on top of the day job | Take work off the plate during the transition |
| Drifting back to old habits | Incentives still reward the old way | Align what is measured, asked about, and recognized |
Good people rarely resist change for no reason. When you find the reason, you usually find a better change, too.
Resistance is rarely the end of the conversation. Most of the time, it is the beginning of the useful one.
Let's talk
If you are leading a change and the resistance is coming from people you respect, I am always happy to compare notes. LinkedIn is the best place to reach me.