Change ManagementIntermediate6 min read

Resistance Diagnostic

Resistance diagnostic is the structured analysis of WHY specific groups are resisting a change, so the response can be targeted instead of generic. Resistance has at least 6 distinct root causes, and each requires a different intervention: (1) lack of understanding (the employee doesn't get what's changing or why), (2) perceived loss (the change costs them status, relationships, autonomy, or comp), (3) lack of capability (they don't have the skills the new state requires), (4) lack of trust in leadership (they've seen prior promises broken), (5) competing priorities (the change conflicts with other things they're being measured on), (6) values misalignment (the change violates something they genuinely believe is right). Treating all six the same with 'more communication' is the most common change-management mistake. The diagnostic is what unlocks targeted intervention.

Also known asResistance AnalysisResistance Root-Cause DiagnosticWhy-People-Resist Diagnosis

Challenge a friend Browse library

The Trap

The trap is interpreting all resistance as 'people don't understand the change.' This is the comfortable interpretation because the fix (more communication) is cheap and doesn't require leaders to do anything hard. Most resistance is NOT a comprehension problem — it's a perceived-loss problem, a capability gap, or a trust problem. Generic 'more town halls' addresses none of these and often makes resistance worse because employees correctly perceive that leadership is treating their concerns as ignorance. The other trap is moralizing resistance ('people just need to get on board'). Resistance is information, not a character flaw — every resistant person is sending a signal about something the change design has not addressed.

What to Do

Run a structured resistance diagnostic in three steps: (1) Listen — focus groups and 1:1s with affected employees, asking 'what would have to be true for you to be fully on board with this?' Categorize responses against the 6 root causes. (2) Map — for each affected group, identify which 1-2 root causes dominate. Different groups will have different root causes for the SAME change. (3) Match the intervention — comprehension gaps need clearer story; perceived-loss needs explicit naming + mitigation (sometimes compensation); capability gaps need training BEFORE expectation changes; trust gaps need leader behavior changes (deliver smaller promises first); priority conflicts need formal goal/comp alignment; values conflicts need either accommodation or accepting that some employees will leave. The diagnostic is the artifact that prevents one-size-fits-all responses.

Formula

Resistance Targeting Score = (% of affected groups with diagnosed root cause) × (% with matched intervention) — score >70% indicates disciplined targeting; <30% indicates generic-response default

In Practice

Prosci's 'Top Reasons People Resist Change' research (now in its 11th iteration as part of the Best Practices study) consistently identifies the same dominant causes across thousands of projects: lack of awareness/understanding of the need for change (~40%), impact on current job/role (~30%), and perceived negative impact on the individual (~20%) lead the list. Critically, Prosci's research shows that the SAME change typically generates DIFFERENT dominant resistance causes across different employee groups — frontline workers most often resist due to perceived job-impact, while middle managers most often resist due to loss of authority/scope. This is why generic resistance-management strategies fail: the intervention that works for frontline (clear job-future communication) does nothing for middle managers (who need authority/scope conversations). McKinsey's parallel research on transformation failure (multiple studies, 2009-2020) consistently identifies 'employee resistance' as a top-3 cited cause, with the deeper finding that resistance is almost always rooted in untreated perceived-loss, not lack of communication. Sources: Prosci Best Practices in Change Management (2020); McKinsey 'How to beat the transformation odds' (Bucy/Schaninger/VanAkin/Weddle, 2017).

Pro Tips

01
Ask 'what would have to be true for you to be fully on board?' instead of 'why are you resisting?' The first question elicits actionable information; the second is interpreted as accusatory and produces defensive non-answers. The phrasing matters because resistance diagnosis lives or dies on the quality of the listening.
02
Resistance from middle managers is almost always about loss of authority or scope, not about the change itself. Middle managers will articulate it as 'the change is poorly designed' because that's the socially acceptable framing — but the underlying signal is structural. Address the structure (their new role, span, comp) and most of the resistance dissolves.
03
Some resistance is correct. Not all resistance is dysfunction; sometimes the change is genuinely badly designed and the resistant employees are seeing it more clearly than leadership. The diagnostic should be honest enough to surface 'the change itself needs to be modified' as a possible outcome, not just 'we need to manage resistance better.'

Myth vs Reality

Myth

“Resistance is irrational — people just don't like change”

Reality

Decades of research (Prosci, McKinsey, Kotter) show resistance is overwhelmingly rational. Employees resist when the change has identifiable costs to them (status, comp, autonomy, relationships, identity) that haven't been acknowledged or mitigated. Treating resistance as irrational is a leadership cop-out that prevents the actual diagnostic work.

Myth

“Communication alone can overcome resistance”

Reality

Communication addresses one of the six root causes (comprehension). It is useless or counterproductive against the other five. A capability gap can't be talked away; perceived loss can't be talked away; broken trust can't be talked away (only rebuilt through demonstrated behavior). Communication-only resistance strategies have a documented failure rate of 60-70% in major transformations.

Try it

Run the numbers.

Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.

🧪

Knowledge Check

You're rolling out a new sales methodology. Frontline reps say 'we don't understand why we need a new system.' Middle managers say 'the change is poorly designed.' Senior sales leaders are silent. What's the most likely diagnostic interpretation?

Industry benchmarks

Is your number good?

Calibrate against real-world tiers. Use these ranges as targets — not absolutes.

Resistance Root-Cause Distribution (typical major change)

Distributions often overlap (one employee can have multiple causes); percentages reflect dominant cause attribution

Lack of awareness/understanding

~40%

Impact on current role/job

~30%

Perceived negative personal impact

~20%

Lack of capability/skills

~15%

Lack of trust in leadership

~10-15%

Source: Prosci 'Best Practices in Change Management' research (multiple iterations, 2007-2020)

Real-world cases

Companies that lived this.

Verified narratives with the numbers that prove (or break) the concept.

🏥

Hypothetical: Mid-Sized Hospital System EHR Rollout

Hypothetical scenario based on Prosci-style diagnostic patterns

mixed

A hypothetical regional hospital system rolling out a new electronic health record (EHR) discovered that the same 'doctor resistance' it had labeled monolithically actually decomposed into three distinct groups under diagnostic analysis: senior physicians (resistance root: perceived loss of clinical autonomy from new structured-charting requirements), nurses (resistance root: capability gap in the new charting interface, plus extra documentation time), and residents (resistance root: comprehension — they hadn't been included in training rollout). Each group required a distinctly different intervention — physician steering committee with documentation flexibility for the seniors, additional one-on-one shadowing for nurses, and integration into the resident education curriculum for residents. Generic 'EHR change management' communication had failed for 6 months because it addressed none of the three actual root causes.

Original Diagnosis

'Doctor resistance' (monolithic)

Diagnostic Reveal

3 distinct groups, 3 root causes

Generic Response Failure Window

~6 months wasted

Targeted Intervention Window

~4 months to adoption recovery

Categorical labels for resistance ('doctors hate it,' 'sales doesn't get it') are diagnostic shortcuts that prevent real intervention. The diagnostic discipline is decomposing labels into specific groups with specific root causes.

Decision scenario

Diagnosing Resistance to a New Performance Management System

You're the CHRO of a 5,000-person company rolling out a new performance management system replacing annual reviews with quarterly check-ins. Six months into rollout, adoption is at 35% (target was 80%). You commissioned a pulse survey: managers report 'too much overhead,' employees report 'no real change in feedback quality,' executives say 'managers aren't taking it seriously.' Three different stories from three different layers.

Adoption Rate

35% (vs 80% target)

Distinct Resistance Stories

3 (one per layer)

Months Since Launch

Default Response So Far

More email comms

Decision 1

First decision: how do you diagnose what's actually going on?

Run focused listening sessions with each layer separately, asking 'what would have to be true for you to fully adopt this system?' Categorize responses against the 6 resistance root causes.Reveal

The diagnostic reveals: managers' resistance is a CAPABILITY gap (they were trained on the system but not on how to actually run a quarterly check-in conversation — different skill) AND a competing-priorities issue (their goals are still annual). Employees' resistance is a TRUST gap (managers' check-ins feel performative because the underlying conversation skill is missing). Executives' resistance is a perceived-effort issue (they don't want to do their own quarterly check-ins). Each layer needs a different intervention. Within 90 days of targeted intervention (manager coaching skills training + executive accountability + goal realignment), adoption climbs from 35% to 71%.

Adoption Rate (90 days): 35% → 71%Manager Capability Score: +3 points (5-point scale)Diagnostic Accuracy: Targeted (vs. generic)

Send a series of CEO communications emphasizing the importance of the new system and the consequences for non-adoptionReveal

The CEO comms address none of the three actual root causes. Managers feel pressured but still lack the conversational capability. Employees feel their managers are even more performatively going through the motions. Executives correctly perceive that the CEO is venting frustration without offering structural support. Within 60 days, adoption marginally rises to 42% but quality of check-ins (per employee survey) actually declines. The diagnostic was skipped, so the response is generic — and counterproductive.

Adoption Rate (60 days): 35% → 42%Check-in Quality: DeclinedManager Cynicism: Increased

Related concepts