People rarely resist change itself. They resist being changed.
That small distinction explains most of the change efforts I've seen stall. A new process, a reorganization, a decision that's already been made: when people push back, leaders tend to label them difficult, afraid, or stuck. Usually something else is going on. Their autonomy feels threatened. They weren't part of shaping the thing they're now being asked to accept.
Why resistance makes sense
Your brain treats loss of control as a threat. When a change lands on people without their input, the brain's alarm system responds the same way it would to any other risk: guarded, defensive, slow to commit. Nobody decides to feel that way. It happens before conscious thinking catches up.
In NLP we work from a simple principle: people move toward their own goals, not yours. The moment someone feels like a variable in your plan instead of a participant in a shared one, resistance is the rational response.
So the question shifts from "How do I get past their resistance?" to "What is their resistance telling me?"
Resistance is information
When someone pushes back, they're usually giving you one of three signals:
- They don't see how the change connects to anything they care about.
- They see a real risk you haven't addressed.
- They feel the decision was made without them.
Each of those is useful. The first tells you to explain the why in their terms. The second may save the project. The third tells you to involve people sooner next time. Leaders who treat resistance as noise miss all three.
How to get real buy-in
The leaders who get commitment don't eliminate change. They move from imposing it to building it with people.
Ask before you tell. Bring people in while their input can still shape the outcome. A meeting held after the decision is sealed, framed as consultation, does more damage than no meeting at all, because people can tell.
Connect the change to what each person wants. The engineer who wants fewer late-night fixes and the sales lead who wants a faster close can both support the same new process once they see what's in it for them.
Watch your language. "We need everyone to get on board" presupposes people are currently off board and need correcting. "Help me find the weak spots in this plan" presupposes they have something valuable to add. The second one gets you better information and more ownership. I wrote more about this in how leaders' questions shape their teams.
Name the loss. Most changes cost people something: a familiar routine, a sense of expertise, a relationship. Saying that out loud ("I know this means letting go of a system you built") calms the alarm far more than pretending the change is pure upside.
Your own state matters
Teams take their cues from the leader's nervous system. If you walk into a change conversation braced for a fight, people feel it and brace back. Before a tough rollout, notice what's happening in your own body. Slow your breathing. Get clear on what you can flex and what you can't. A leader who is steady and honest about the trade-offs is much easier to follow than one who is selling.
Try this week: one early conversation
Pick a change you're planning that hasn't been finalized yet.
- Choose two people it will affect most.
- Before you finalize anything, ask each of them: "What would make this work for you, and what worries you about it?"
- Listen without defending the plan.
- Change at least one thing based on what you hear, and tell them you did.
That last step matters most. People commit to what they helped build, and they remember who listened.
Change goes faster with people
Involving people early can feel slower. In practice it's the fastest route, because you skip the months of quiet resistance that follow a change people never chose.
If trust on your team needs work first, start with how to build trust as a leader, on purpose.
If your organization is in the middle of a change that isn't landing, talk to me about a program for your team.