Resistance to Change: Finding the Cause and Responding Well

Every leader who has introduced a change has met resistance: the meeting where nobody speaks, the quiet return to the old spreadsheet, the colleague who asks the same pointed question for the third time. It is tempting to treat all of it as a problem to overcome.

A more useful starting point is that "resistance" is a label for behavior, not an explanation of it. The same visible pushback can come from fear of loss, honest doubt about the plan, lack of skill or simple exhaustion. Each calls for a different response, and the wrong response can turn mild doubt into real opposition. This guide covers how to tell the causes apart and what to do about each.

Resistance is a label, not a diagnosis

Early research on organizational change, such as Coch and French's 1948 study, framed people's negative reactions as resistance. In a 2009 article in the Journal of Change Management, Achilles Armenakis and Stanley Harris explain why they prefer the term readiness, which they define as "the cognitive precursor of the behaviors of resistance to or support for organizational change." Their emphasis is on creating readiness up front rather than waiting to reduce resistance once it appears.

Sandy Kristin Piderit, writing in the Academy of Management Review in 2000, argued for rethinking resistance as multidimensional attitudes toward a change. Her article highlights ambivalence. In practice, one person might support the goal, doubt the plan and dread the extra workload all at once. Lumping that person in with "resisters" misses the parts of their view you could work with.

Common sources of pushback

Armenakis and Harris describe five beliefs that underlie people's motivation to support a change. Read in reverse, they are a map of where pushback tends to come from:

• Discrepancy: "I don't see why we need to change." The case for change hasn't landed.
• Appropriateness: "We need to change, but this is the wrong fix." The person may see a flaw you don't.
• Efficacy: "We can't pull this off," or "I can't." This is often about skills, time or tools.
• Principal support: "Leaders won't stick with it." Their phrase for the worry is that the change is another passing fad or "program of the month."
• Valence: "This is worse for me." The person sees costs to themselves and no benefit.

Loss deserves its own line. The Bridges Transition Model, developed by William Bridges, holds that transition begins with an ending, as people identify what they are losing, which may include relationships, processes, team members or locations. Pushback that sounds like an argument about the plan is sometimes grief about what the plan takes away.

Listen before you persuade

The quickest way to find the cause is to ask, privately and with genuine curiosity. Some questions that map to the five beliefs:

1. "What do you think is driving this change?"
2. "If you were designing it, what would you do differently?"
3. "What would make this hard for you or your team to do well?"
4. "What would convince you that leadership is serious about this?"
5. "How do you expect this to affect your day-to-day work?"

Then listen without defending the plan. You are gathering information, not winning a debate. Notice which question produces the strongest reaction; that is usually where the real concern sits.

Match the response to the cause

Once you know the cause, the response tends to follow:

• No sense of need: share the evidence behind the change in concrete terms, including what happens if nothing changes.
• Doubt about the fix: invite the critique in detail and be willing to change the plan where it's right. If you can't change it, explain why the alternatives were rejected.
• Doubt about ability: provide training, practice time, job aids and a clear person to ask. Reduce other demands during the learning curve.
• Doubt about follow-through: let leaders' behavior answer it. Leaders use the new process themselves, keep funding it and talk about it after launch.
• Personal cost: be honest about it. Where you can reduce the cost, do; where you can't, say so plainly rather than pretending everyone wins.
• Loss: acknowledge what is ending and, where it fits, mark it, rather than rushing straight to the new beginning.

Prosci's ADKAR Model offers a similar discipline. Its five elements are Awareness, Desire, Knowledge, Ability and Reinforcement, and Prosci advises identifying the earliest point where someone is stuck and focusing support there. Training someone who doesn't yet see why the change matters rarely works.

Involve people in the how

Armenakis and Harris note that active participation by the people affected can strengthen both valence and efficacy, letting them work on the difficulties they face and choose changes they believe they can accomplish. A U.S. General Accounting Office report on mergers and transformations (GAO-03-669) lists involving employees among its key practices, including using employee teams and incorporating employee feedback into new policies and procedures.

Even when the decision itself is set, the details usually aren't. For example, imagine a hypothetical distribution center moving to a new pick-and-pack process. Leadership has decided to make the change, but a team of experienced pickers could design the station layout, test it for a week and adjust it. The skeptics on that team often become its most credible advocates, because their concerns visibly shaped the result.

Be clear about what is and isn't open

Involvement only builds trust if it is honest. Say plainly which parts are decided and which are open for input. Asking for feedback on a decision that has already been made, then ignoring it, deepens cynicism.

Some limits are firm. Safety requirements, legal obligations and decisions already made by the organization are not up for debate, and saying so clearly is a kindness. If, after real listening, support and time, someone still refuses to work in the new way, that becomes a performance conversation. Handle it as you would any other: privately, with clear expectations, documentation and support from HR, and with the same standard applied to everyone.

Look after yourself and your team

Leading people through change they didn't choose is draining for everyone, including the leader. If you or someone on your team is struggling well beyond ordinary stress, encourage them to use your employee assistance program if you have one, or to talk with a health professional. This guide is not a substitute for professional care. In a crisis in the US, call or text 988, and if someone is in immediate danger, call 911.

Key takeaways

• Treat "resistance" as a symptom, and diagnose the cause before responding.
• People can be ambivalent, supporting a change in some ways and doubting it in others.
• The five beliefs (need, right fix, ability, leader commitment, personal benefit) plus loss cover most sources of pushback.
• Match the response to the cause: evidence, plan changes, training, visible leader commitment, honesty about costs or acknowledgment of loss.
• Involve people in shaping how the change works, and be honest about what is already decided.

Sources

• Achilles A. Armenakis and Stanley G. Harris, Reflections: our Journey in Organizational Change Research and Practice, Journal of Change Management (2009)
• Sandy Kristin Piderit, Rethinking Resistance and Recognizing Ambivalence: A Multidimensional View of Attitudes Toward an Organizational Change, Academy of Management Review (October 2000)
• William Bridges Associates, Bridges Transition Model
• Prosci, The Prosci ADKAR Model
• U.S. General Accounting Office, Results-Oriented Cultures: Implementation Steps to Assist Mergers and Organizational Transformations, GAO-03-669 (July 2003)