Why 'Resistance' Is Often the Wrong Diagnosis

A label ends the investigation too early

When a stakeholder delays, argues, withdraws, keeps using the old process or openly challenges the program, the project often compresses all of that into one word: resistant.

The word may describe what the project is experiencing. It does not tell us why it is happening. And if the diagnosis is wrong, a perfectly executed intervention can still fail.

Prosci's ADKAR® Model gives me a useful first map: Awareness, Desire, Knowledge, Ability and Reinforcement. If someone does not understand why the change is needed, I look first at Awareness. If the person wants to change but does not know how, Knowledge gives me a direction. If the person knows but cannot perform, Ability deserves attention. The difficult cases are often people who understand the change and may even know how to execute it, but still do not want to support it. 'Desire is low' locates the barrier; it does not explain it. That is where I slow down rather than pushing more communication.

Resistance usually has more than one source

Across transformation programs, I usually look in four places before I blame attitude: the change itself; the person's history and interpretation; the manager, sponsor and incentive system around them; and the wider environment — trust, workload, resources and culture. Real cases often combine more than one.

Prosci's 12th Edition research points to many of the same recurring issues: poor understanding of the change, fear of the unknown or role impact, weak leadership support, limited involvement, competing workload and resources, and misaligned incentives. Managers add another layer because they can understand the change and still doubt the solution, fear losing control or status, or simply not feel equipped to lead their teams through it.

AI makes this easier to misread. Concern about an AI-enabled process may be fear of a new technology, but it may also be a sensible question about role boundaries, accountability, visibility of work, data quality or whether the proposed use case is mature enough for this business. The label “resistance” does not tell me which one.

When the pattern sits mainly in sponsorship, incentives or decision rights, the related article Why Transformation Governance Breaks When Everyone Owns a Different Definition of Success is the better next read.

Start with what actually changed for the person

My first question is what the change is actually doing to this person. Is workload increasing? Is decision authority moving? Is expertise becoming more visible or less valuable? Is the role changing? Is a manager losing autonomy? Is performance becoming more transparent?

In some long-tenured organizations I work with across Egypt and the Gulf, ERP does more than change steps: it moves knowledge from a person's head into shared data and process. A veteran operator can hear “standardize the process” as “the thing that made me indispensable is becoming visible and transferable.” That context changes the management question from “Why is he difficult?” to “What is the future role of his expertise?”

Then I separate the visible reaction into three lenses: what the person thinks, what the person feels and what the person does. I use Think-Feel-Act as a practical shorthand, not as a proprietary model.

A person can believe the project is sensible, feel anxious about the implications and still fall back to an old behavior under pressure. Another can behave compliantly while privately believing the design will fail. Treating those as the same 'resistance' wastes information.

Personality matters. Context matters too

Some people prefer routine, react more strongly to uncertainty or need more evidence before they move. That matters. But the same person can support one change and resist another because the context changed — trust, role impact, sponsor credibility, incentives or timing. Oreg's research is useful to me for exactly this reason: both dispositional tendencies and organizational context have been associated with reactions to change.

I do not use that to turn managers into psychologists or to predict resistance from a personality label. I use it as a reminder not to choose between “the person” and “the context” too early.

Personality is a lens, not a verdict

People differ in how they process information, evaluate risk, respond to uncertainty and build trust. Those differences can help a manager choose a better conversation. A strategic thinker may need the logic and consequences tested. A detail-oriented operator may trust a measured trial more than a future-state speech.

Personality should never become a convenient explanation for a bad process, weak sponsor, misaligned incentive or damaged trust. It can help me choose how to communicate and test assumptions; it should not become a verdict on who will support or resist the change.

Find the question behind the objection

The most useful outcome of diagnosis is often a better question.

Instead of 'How do I make the warehouse key user accept standard?' the real question may be 'Why has the business not resolved the return policy or storage requirement the standard process depends on?' Instead of 'How do I force treasury to use the new reconciliation flow?' the question may be 'Has management provided the capacity, banking integration or role design required to make the process viable?'

Accountability comes after diagnosis

Once the case is fair and the required support exists, accountability is legitimate; the related article Before You Manage Resistance, Make Sure the Change Is Worth Defending develops that sequence.

When the question changes, the solution often changes with it.