Before You Manage Resistance, Make Sure the Change Is Worth Defending

Resistance is information before it is a problem

Before I ask how to overcome resistance, I want to know whether the change itself is worth defending. A project can be technically coherent and still ask people to absorb a broken process, an unresolved policy, an unrealistic workload or a real loss that nobody has acknowledged.

I have become much more cautious with the label “resistance.” Sometimes the objection is weak, political or self-protective. Sometimes it is the first useful signal that the change itself has a design problem. The management task is to find out which one you are dealing with before choosing the response.

Prosci's recent resistance guidance makes a similar practical point: resistance should be understood, and much of it can be prevented through better planning rather than treated only after it appears. In Prosci's 2023 Best Practices research, 43% of respondents said that more than half of the manager resistance they experienced could have been avoided. That does not mean every objection is valid. It does mean prevention and diagnosis deserve more attention than labels.

Build a fair case before asking for commitment

A change is easier to defend when four things are reasonably true: the business problem is real, the proposed response is coherent, the burden on affected people has been understood, and the organization has provided the conditions needed to execute the new way of working.

I use 'fair case' as a practitioner question, not a scientific model. It forces the project team to look at the change from the receiving side before judging the receiver.

• Is the business reason visible beyond the project team?
• Is the future process actually workable under realistic operating conditions?
• Have we recognized legitimate losses in role, autonomy, status, workload or expertise?
• Are the data, capacity, policies, tools and decision rights needed for the new process actually available?

A rational objection can look behavioral from the project room

Imagine a warehouse or finance team continuing an offline step after go-live. The behavior is visible; the cause is not. It may be habit. It may be deliberate refusal. But it may also be a missing policy decision, an approval design that cannot meet operating speed, or a capacity gap that makes the official process unworkable.

If the project treats every bypass as an attitude problem, it can end up communicating harder about a process that still needs fixing. That creates a credibility problem: the people closest to the work can see the gap, while the project insists the problem is their mindset.

Standardization needs business judgment, not ideology

ERP standardization is one of the most common triggers of legitimate objection, and the trade-off deserves its own treatment: Standardize Without Creating Shadow Work. The point here is narrower: when the standard design itself is not defensible under real operating conditions, resistance management is the wrong first intervention.

Sometimes people are losing something real

Transformations redistribute more than tasks. They can redistribute information, visibility, decision rights and status. A plant manager who loses planning authority, an experienced key user whose informal expertise becomes less central, or a function whose local optimization is replaced by an end-to-end process may be reacting to a real loss.

In one family-owned industrial group, management had a genuine commitment not to dismiss long-serving people; roles would change rather than jobs disappear. That reduced the fear of unemployment, but it did not remove the loss of authority, prestige and identity when activities previously owned by plant managers were centralized. The change could still be right for the company and painful for individuals at the same time.

AI makes the fair-case test more important

AI sharpens the same question. If an AI-enabled process is expected to automate part of a role, move decision rights or make work more transparent, telling people that AI is strategic is not enough. I want the organization to be clear about what will change, what remains a human decision, how accountability will work, what skills will be needed and what commitment management is making to the people affected.

That does not mean waiting until every answer is perfect. It means not calling a reasonable concern “resistance” when the organization itself has not made the change concrete enough for people to judge.

Listening is not surrender

Testing whether the change is worth defending does not mean every objection wins. Transformation would become impossible if every local inconvenience had veto power over enterprise value.

The sequence matters. First understand the objection. Fix what is genuinely broken. Acknowledge legitimate loss. Reduce avoidable burden. Make the enterprise trade-off explicit. Then, once the case is fair, the decision is clear and the required support exists, accountability becomes legitimate.

Key takeaway

Before asking, 'How do we overcome resistance?' ask a harder question: 'What exactly are we asking people to defend with us?' If the case is weak, improve the change. If the case is strong, lead it clearly.