Executives often interpret resistance as attitude: people are negative, change-averse, political, slow, cynical, or unwilling to get on board.

Sometimes that is true. More often, resistance is rational.

People resist changes that make their work harder, reduce their status, remove their control, expose their performance, threaten their expertise, increase their risk, add work without removing work, or break the informal systems they use to get things done.

Treating that resistance as a communications problem is a mistake. Resistance is data about the current operating system and the losses created by the new one.

Every change creates loss

Even good changes create loss for someone.

A new approval process may reduce chaos but remove a leader's informal veto. A new CRM discipline may improve forecasting but expose weak pipeline quality. A new operating cadence may clarify accountability but reduce the ability to hide behind group ownership. A new self-serve tool may improve speed but reduce the gatekeeping power of an expert team. A move upmarket may create strategic value but make some employees feel less competent in the new motion.

If leaders talk only about the upside, people will still feel the losses. They will just discuss them privately.

The mature move is to name the loss without surrendering to it. People can handle an honest tradeoff better than a cheerful fiction. "This will reduce local discretion because we need cleaner enterprise pricing" is more credible than "nothing really changes for you." Naming the loss also lets leaders decide what to compensate, what to sequence, and what to hold firm on.

Power is part of adoption

Change often redistributes power. Who gets to decide? Who has access to information? Who controls exceptions? Who owns the customer relationship? Who can approve resources? Who defines quality? Who sees the dashboard first?

When power shifts, resistance is predictable.

This does not mean the change is wrong. It means adoption requires explicit decision rights and consequences. If the company says authority is moving to the front line but executives continue to override decisions through side channels, the old power system wins. If the company says finance now owns investment discipline but functional leaders can bypass finance by escalating to the CEO, the new system is decorative.

Power has to move in behavior, not in slides.

Workload resistance is not laziness

Many changes fail because they add work while pretending not to.

People are told to use a new system while maintaining the old one. Managers are asked to coach differently while keeping the same meeting load. Teams are asked to adopt new planning practices without reducing existing reporting. Reps are asked to improve data hygiene without getting faster workflows or clearer value from the data.

Then leaders wonder why adoption is low.

If the new behavior adds load, the change plan must remove, simplify, automate, sequence, or compensate elsewhere. Otherwise people will protect their capacity by reverting to the old way.

That is not irrational. That is survival.

Map resistance before judging it

Use a resistance/loss map:

  • Status loss: Who becomes less central, less expert, or less visibly important?
  • Control loss: Who loses approval rights, information control, or exception power?
  • Competence loss: Who has to operate in a domain where they feel less skilled?
  • Speed loss: Where does the new process initially feel slower?
  • Identity loss: Which teams feel the change contradicts how they see their role?
  • Workload increase: What work is added before old work disappears?
  • Risk increase: Who becomes more exposed if the change fails?
  • Trust gap: Where have previous changes created cynicism?

This map does not give everyone a veto. It gives leaders a more accurate adoption plan. For each loss, choose a response: redesign the change, provide support, sequence more carefully, compensate with another benefit, or explicitly accept the loss because the business reason is strong enough. Unanswered loss turns into quiet resistance.

Use resistance to improve design

Some resistance is a sign that people are protecting a broken old system. Some resistance reveals that the new system is badly designed.

The difference matters.

If people resist because they can no longer hide poor quality, proceed. If they resist because the new workflow ignores a critical customer exception path, fix the workflow. If managers resist because they do not want accountability, hold the line. If managers resist because they have no practical way to reinforce the change, give them the tools.

The point is not to appease resistance. The point is to diagnose it.

The operator's stance

Do not romanticize resistance. Do not demonize it either.

Ask: what does this resistance make rationally visible?

The answer will usually tell you what must change around the change.