Resistance & Support Map

Map who supports, doubts or resists a change and why, answer each reason with a response that fits it, and plan what has to be in place for people to actually work the new way.

Reactions to change and change readiness are strong research (Rafferty, Jimmieson & Armenakis, 2013), with a contested early classic (Coch & French, 1948). Diffusion of innovations is strong as a descriptive theory (Rogers, 2003); using adopter timing for internal change is an extension. COM-B is mixed research (Michie, van Stralen & West, 2011). Matching responses to causes (Kotter & Schlesinger, 1979), the force field and the checklists here are practice, not research. Scores and timings on this page are rules of thumb.

Use it when:

• You have decided on a change and people are pushing back, going quiet or adopting slowly.
• You want to plan the launch so different groups get the support they actually need.
• A change has launched and you need to see where it is stuck and why.

Skip it when:

• You have not yet checked whether the timing and support are there: start with 3.7 Change Context Scan.
• The pushback is about power and interests among a few senior people: use 3.1 Stakeholder Map and 3.2 Power & Influence Grid.

Resistance is often less about the change than about how it arrives. An early factory study reported that groups who helped design a work change took it up more readily than groups who had it imposed (Coch & French, 1948); later critics questioned how that study was read, so treat it as suggestive. Research on change readiness has since sharpened the point: people judge whether the change is right, whether management means it, whether they can manage it and what it means for them, and those judgments shape support or resistance (Rafferty, Jimmieson & Armenakis, 2013). Kotter and Schlesinger's (1979) practical contribution was a menu: different causes of resistance, such as self-interest, misunderstanding, low tolerance for change or a different reading of the situation, call for different responses, from education and participation to, rarely and at a cost, coercion.

So diagnose before you respond: the same silence can mean confusion, a sound objection or exhaustion. And treat the skeptic as a source: their reason is often the best data you have.

List the groups the change touches, by role, not by name. Write their stance, where they are likely to fall in adoption timing (early, middle, late), and their main reason in words they would use.

Strong answer: "Night-shift lab technicians: resist; late. 'The scanners failed twice last winter and we were the ones left with the queue.'" Not: "Some older staff are negative."

Adoption timing follows Rogers (2003), whose categories describe when people take up a given innovation, not their personality. Population shares vary by context, so none are given here.

Illustrative example: the roles, the organization and all numbers are made up.

The lab manager at a Norwegian hospital laboratory is moving sample labeling from hand-written labels to bedside scanning.

Step 1: Day-shift nurses support it, early. Ward clerks are ambivalent, middle: "Who fixes the printer?" Night-shift technicians resist, late: "The scanners failed twice last winter."

Step 2: The senior night technician reads the situation differently and has a point: the scanners did fail. Response: she leads the night test and designs the fallback. A ward clerk worries about extra work (self-interest); the response is a clear task list and a named contact.

Step 3: For: fewer mislabeled samples (4). Against: no fallback at night (4), and missing scanners on two wards (3). The manager reduces the fallback gap first.

Step 4: Capability is fine. Opportunity is the gap: two wards lack scanners, and colleagues still accept hand-written labels. Motivation follows once the fallback is tested.

Step 5: Weekly bedside scan share; red flag if nights lag days after four weeks; checkpoint at week six. The manager briefs the elected representatives before go-live.