“People resist change” is one of the most repeated ideas in leadership, and it’s imprecise in a way that leads directly to the wrong interventions. Framed that way, resistance looks like an irrational aversion to anything new—something to be managed with enthusiasm, better communication, or simply more persistence in pushing the change through. That framing misses what’s actually happening in almost every case of genuine resistance: people aren’t reacting to change in the abstract. They’re reacting to specific, identifiable losses the change represents to them, and those losses are frequently real, even when the change overall is the right call for the organization.
This distinction matters because it points to a different diagnostic question. Instead of asking “why are people resisting this change,” which tends to produce answers about fear or inertia, the more useful question is “what, specifically, does this person stand to lose”—and the answer is almost always concrete. A reorganization that’s clearly right for the business might mean a manager loses direct authority over people they’ve developed for years. A new system that’s genuinely more efficient might mean an employee loses the expertise that made them valuable, replaced by a tool that renders years of hard-won skill less relevant. A strategic pivot might mean a team loses the identity and mission that made their work feel meaningful, even if the new direction is more commercially sound. None of these losses are imaginary or irrational. They’re real costs borne by real people, and no amount of enthusiasm about the change’s benefits erases them for the person actually experiencing the loss.
Why More Persuasion Misses the Point
Leaders who treat resistance as irrational tend to respond with more persuasion about the change’s merits—better data, a more compelling vision, a clearer articulation of why the change is necessary. This rarely works, because it’s answering a question no one actually asked. The person resisting usually already understands, intellectually, why the change makes sense. Their resistance isn’t about being unconvinced of the logic. It’s about the logic not addressing what they’re actually losing, which persuasion about the change’s benefits does nothing to acknowledge, let alone resolve.
Name the Loss Before the Destination
The more effective approach starts with naming the loss directly, before addressing anything else. This is uncomfortable, because it requires a leader to sit with something less flattering than “here’s why this change is exciting”—it requires saying, plainly, “I understand this means you’re giving up X, and I’m not going to pretend that isn’t real.” That acknowledgment doesn’t make the loss disappear, and it isn’t supposed to. What it does is signal that the leader has actually seen the full picture, rather than a version of it filtered through only the benefits—and that signal is frequently what determines whether someone moves toward the change with genuine engagement or complies with it while quietly working against it in whatever ways remain available to them.
Ask what, specifically, this person stands to lose—not why they’re resisting change.
Address the Loss, or Be Honest About Sacrifice
Once the loss has been named honestly, there’s real work to be done in addressing it directly, rather than working around it. Sometimes that means finding a genuine replacement for what’s being given up—new scope for the manager who lost direct authority, a new form of expertise to build for the employee whose old skill was automated away. Sometimes it means being honest that there isn’t a full replacement available, and that the organization is asking for a real sacrifice in service of something larger, which is a harder conversation but a more honest one than pretending the loss doesn’t exist. Either way, the conversation has to engage with the actual loss, specifically, rather than staying at the level of the change’s overall merits.
There’s a leadership habit worth building directly from this: before rolling out any significant change, do the work of identifying, concretely, who loses what—not in the aggregate, but by name where possible. That exercise, done honestly, changes how the change gets communicated, because it surfaces exactly which conversations need to happen individually, with specific acknowledgment, rather than being handled through a single organization-wide announcement about why the change is good for everyone.
None of this means every loss can or should be avoided—some real losses are simply the cost of a change that’s genuinely necessary, and pretending otherwise doesn’t help anyone. But naming the loss honestly, rather than talking past it with enthusiasm about the destination, is usually what separates a change that gets genuinely adopted from one that gets quietly resisted for years after it’s technically been implemented.
If you’re leading a change and the resistance to it doesn’t quite add up given how sound the logic is, the missing piece is often a loss that hasn’t yet been named. Explore coaching services.
Frequently asked questions
Do people resist change—or something else?
They resist loss. Resistance is usually a reaction to specific, identifiable losses the change represents—authority, expertise, identity—not an irrational aversion to anything new. Those losses are often real even when the change is right for the organization.
Why doesn’t more persuasion about the change’s merits work?
People often already understand the logic. Resistance isn’t about being unconvinced of the benefits—it’s that the benefits don’t address what they’re actually losing. Persuasion about merits talks past the loss.
What should leaders do instead?
Name the loss directly first. Then replace what’s given up where possible, or be honest that a real sacrifice is being asked. Before rollout, identify who loses what by name—and have those conversations individually.