Why Do People Resist Change Even When Change Is Necessary?

People don’t resist change because they’re stupid. That’s the lazy explanation, and it has survived in management conversations far longer than it deserves.

They also don’t resist change simply because they “hate change.” Most people change constantly: they learn new tools, move cities, become parents, adapt to crises, change diets, switch phones, migrate from one app to another without a workshop, a sponsor roadmap, or a laminated change curve. So when employees resist an organizational change that is, on paper, necessary — a new ERP system, a restructuring, an AI rollout, a cost programme, a new operating model — something more interesting is happening.

The short answer is this: people resist necessary change when the change threatens something they value, when the case for change is not trusted, when the path feels unsafe or unfair, or when the proposed solution looks worse than the current pain.

That last part is awkward. A change can be necessary and still badly designed.

Resistance is not one thing

The research literature has been trying to correct a managerial misunderstanding for decades: “resistance” is not a single behaviour or attitude. It can be cognitive, emotional, and behavioural. Someone may intellectually agree with the change but feel anxious about it. Another person may feel emotionally excited but quietly doubt the plan. A third may comply in public and preserve the old workaround in private.

Piderit’s well-known article on resistance argues that responses to change are often ambivalent and multidimensional, not simply “support” or “resistance.” She pushed researchers to see employee responses as attitudes with cognitive, emotional, and intentional components rather than as a blunt yes/no reaction.

Oreg, Vakola, and Armenakis later reviewed quantitative studies of change recipients’ reactions across a long historical period. They examined studies published between 1948 and 2007 and found 79 quantitative studies that met their criteria. Their model grouped reactions into tridimensional attitudes and linked them to antecedents such as change-recipient characteristics, internal context, change process, perceived benefit or harm, and change content.

That matters because the same employee can say:

• “Yes, the current process is broken.”
• “No, I don’t trust this solution.”
• “Maybe I can learn it.”
• “But I’m not convinced leadership will support us when productivity drops.”

Is that resistance? Support? Realism? Ambivalence? Probably all of it.

Necessary does not mean legitimate

Leaders often assume that if the business case is rational, employees will eventually align. But people don’t respond only to the abstract necessity of change. They respond to the perceived legitimacy of the specific change.

Holt, Armenakis, Feild, and Harris developed a readiness-for-change scale based on data from more than 900 organizational members. Their findings suggest that readiness depends on several beliefs: whether employees believe they can implement the change, whether the change is appropriate, whether leaders are committed, and whether the change has personal benefit.

This is one of the simplest and most useful ideas in the field: people may accept the need for change but reject the proposed answer. A company may genuinely need to improve productivity. That does not automatically mean employees will accept a poorly explained restructuring. A business may need AI adoption. That does not mean people will trust a vague “AI-first” agenda.

The five beliefs behind acceptance or resistance

Armenakis and colleagues developed the Organizational Change Recipients’ Beliefs Scale around five beliefs: discrepancy, appropriateness, efficacy, principal support, and valence. The instrument was designed to act as a barometer of buy-in and to identify belief gaps that can damage change success.

In practical language, employees ask five questions:

• Discrepancy: Is there really a problem?
• Appropriateness: Is this the right solution?
• Efficacy: Can we actually do this?
• Principal support: Are credible leaders and influencers genuinely behind it?
• Valence: What does this mean for me?

If one of these beliefs is weak, resistance becomes more likely. Not because people are irrational, but because the change message has not survived contact with lived experience.

People fear losses more than they value promised gains

Necessary change is usually sold through gains: better systems, faster decisions, improved customer service, stronger competitiveness, cleaner data, lower cost. That sounds reasonable. The trouble is that employees often experience change first as loss. They may lose competence in a familiar process, status as the person who knows the old system, control over local decisions, relationships built around current workflows, speed at least temporarily, and confidence that they can perform well.

Prospect theory helps explain why this matters. Kahneman and Tversky argued that people evaluate outcomes relative to a reference point and that losses loom larger than gains. In change terms, the current way of working becomes the reference point; even if it is imperfect, it is known. The future benefit may be bigger, but the immediate loss feels sharper.

Samuelson and Zeckhauser’s work on status quo bias adds another layer. Their experiments showed that people disproportionately stick with the current or previous decision, and real-world data from health-plan and retirement-program selections showed substantial status quo bias in important decisions. So when leaders say, “This will be better in twelve months,” employees may hear, “You will be worse at your job next Monday.” That is not a small psychological gap.

Resistance is often a fight for control

Psychological reactance theory is useful here. Reactance is the motivational pushback people experience when they feel a freedom has been threatened or removed. A review of reactance research describes it as the motivation to regain freedom after it has been lost or threatened, which can lead people to resist social influence.

Organizational change often removes choice, or appears to. New process. New system. New reporting line. New approval flow. New metrics. New expectation to use AI. New decision rights. Even when the change is objectively needed, the employee may experience it as a narrowing of agency. This is why tone matters. The same change can be received differently depending on whether people feel invited into a disciplined transition or pushed into obedience.

Sometimes resistance is evidence, not obstruction

Ford, Ford, and D’Amelio argue that prevailing views of resistance often tell a one-sided story that favours change agents. They suggest that change agents themselves may contribute to resistance through their actions or inactions, and that resistance can become a resource for change rather than merely a defect to eliminate.

This always strikes me as important because organizations are very quick to psychologize employee pushback. If users complain, they are “negative.” If managers question the plan, they are “not aligned.” If frontline teams point out operational problems, they are “stuck in the old world.” Sometimes that is true. Often, though, they are telling you the design is weak.

Mathews and Linski make a similar argument in their paper on reevaluating resistance. They challenge the idea that resistance is simply an employee problem and frame resistance behaviours as outward signs that change has disrupted people’s ability to pursue important human goods, such as competence, autonomy, relationships, excellence, or meaning. A person resisting a new ERP process may not be defending laziness. They may be defending competence. A manager resisting an AI decision tool may not be anti-technology. They may be worried about accountability.

Readiness is not capacity, and capacity is not readiness

Organizations often confuse these two. Capacity means having the resources, skills, systems, structures, and time to implement change. Readiness is the shared psychological state in which people are committed to the change and confident that they can implement it. This is why leaders need to assess change readiness as well as delivery capacity.

Weiner’s theory of organizational readiness makes this distinction very clearly. He defines readiness as shared change commitment and shared change efficacy. It depends on how much people value the change and how they appraise task demands, resource availability, and situational factors. This explains a common paradox: an organization can have the budget, consultants, technology, and training materials — and still not be ready. Why? Because people may not believe the task is realistic. A capability plan without a credibility plan is fragile.

ERP shows the problem in a very concrete way

Enterprise systems are a useful example because they expose nearly every reason people resist necessary change. ERP programmes promise integration, data consistency, better planning, and process discipline. But they also alter roles, power, visibility, control, and cross-functional dependencies.

Kwahk and Kim note that enterprise-system implementation often involves multiple stakeholders and fundamental improvements across functional boundaries. They cite estimated failure rates for enterprise-system project goals between 60% and 90%, and argue that failure is not limited to technical issues; it emerges from interactions among people, tasks, environment, and technology.

Caporarello and Viachka argue that ERP changes can be disruptive because they move organizations from functional to process-based operational logic. Their work highlights ERP-specific sources of resistance, including higher control levels, process changes, structural change, the need to acquire new knowledge, and the need to work with greater cross-functional interdependence. So when employees resist ERP, they may be resisting much more than screens. They may be resisting a new organizational logic.

The social side: status, trust, fairness, and belonging

Necessary change often rearranges the social order. Who becomes more important? Who loses informal power? Which expertise becomes obsolete? Which manager gets more control? Which function becomes dependent on another? Who is blamed when the new process fails? These are not sentimental questions. They shape behaviour.

Oreg and colleagues’ review includes internal context, perceived benefit or harm, change content, and change process as antecedents of reactions to change. In other words, people respond not only to the technical content of the change, but also to the way the change is handled and to what they believe it will do to them. This is why fairness is so central. Employees may accept difficult change if the process feels honest, competent, and fair. They may resist even beneficial change if it feels imposed, manipulative, or politically contaminated.

Why “burning platform” messages can backfire

Many change models recommend creating urgency. Fine. Sometimes urgency is necessary. But urgency is not the same as panic, and fear is not the same as commitment. Weiner notes that strategies such as highlighting the gap between current and desired performance may increase readiness by increasing change valence — the sense that the change is needed, important, or worthwhile. But he also warns that there is unlikely to be one best way to increase readiness; creating urgency may help when complacency is high, but may be less useful when uncertainty is already high.

If people are complacent, a sharper case for change may help. If people are already exhausted, frightened, or overloaded, more urgency may simply produce shutdown. The same message that mobilizes one group can overwhelm another.

What leaders should do instead of blaming resistance

The better question is not “Why are they resisting?” It is: “What is this resistance trying to tell us?” A more serious diagnostic approach would ask:

• Do people believe the change is truly necessary?
• Do they believe this specific solution is appropriate?
• Do they believe they can succeed in the new way of working?
• Do they trust leadership support?
• Do they see personal or professional benefit?
• What losses are they anticipating?
• Where does the change threaten autonomy, status, competence, or belonging?
• Which objections are emotional noise, and which are accurate operational intelligence?

Some resistance should be challenged. Some should be absorbed. Some should be thanked, because it just saved the programme from a very expensive mistake.

The uncomfortable truth

People resist necessary change because necessity does not remove fear, loss, mistrust, ambiguity, poor design, identity threat, or political self-protection. A change can be strategically required and psychologically unsafe. It can be economically rational and socially clumsy. It can be technically correct and operationally naive. That is the paradox.

The task of change management is not to “overcome resistance” as if employees were obstacles on a road. The task is to understand the beliefs, losses, constraints, and social meanings behind the resistance — then decide what needs to be explained, redesigned, supported, negotiated, or simply made non-negotiable.

Change is rarely resisted in the abstract. People resist the version of the future they think you are asking them to live in.

For change leaders working through resistance, the Stakeholder Analysis Tool helps make influence and engagement priorities visible. Browse the broader stakeholder analysis resources for related guidance on engagement, sponsorship and communication. When the issue needs a broader evidence review before a critical decision, the Readiness Diagnostic Sprint can turn those signals into focused mitigation priorities.

Resistance is one of several early indicators worth tracking. Explore adoption risk resources for guidance on spotting readiness gaps early and turning them into owned mitigation.