Introduction: why this action matters for adoption
Resistance rarely appears evenly across an organization. One region may adopt quickly while another keeps using spreadsheets. Supervisors may publicly agree but privately delay coaching. A professional group may resist because the change threatens autonomy, quality, incentives, workload, or identity. Treating all resistance as a communication problem usually produces more noise, not better adoption.
This action is a diagnostic assessment and planning intervention. Its purpose is to locate specific pockets of resistance, understand the root causes, and design targeted tactics with the affected group. Resistance should be treated as useful data about adoption barriers, not simply as bad attitude or noncompliance [Prosci, 2025; Kotter & Schlesinger, 1979]. (prosci.com)
What this action is and when to use it
Use this action when adoption risk is concentrated in a specific stakeholder group, site, function, role, union group, management layer, or sponsor coalition. It is especially valuable before go-live, after a readiness pulse shows uneven confidence, when training attendance is low, when managers are inconsistent, or when workarounds appear after launch.
The output is a short findings summary: where resistance is concentrated, what is driving it, which risks matter most, what tactics will be used, who owns them, and how progress will be measured. PMI describes readiness work as examining whether the organization has the resolve, fit, and capacity to deliver the intended benefits, including commitment, culture, and resourcing considerations [PMI, 2014]. (pmi.org)
Preparation: inputs, stakeholders, materials, timing, and decisions needed
Start with evidence, not labels. Review the stakeholder map, impact assessment, training data, adoption dashboard, help desk themes, pulse survey results, manager feedback, change risk log, and known operational constraints. Readiness research suggests looking at whether people believe the change is appropriate, whether leaders support it, whether they personally benefit, and whether they can perform in the new way [Holt et al., 2007]. (journals.sagepub.com)
Invite the right people: the change manager, accountable sponsor, affected people manager, project or product owner, HR or L&D partner, and a small number of credible representatives from the resisting group. Before the session, decide what is negotiable. If the future state is fixed but timing, workflow, training, support, or local sequencing can change, say so. Employee voice is more credible when leaders listen and act on feedback, and when managers are equipped to handle sensitive conversations [CIPD, 2026]. (cipd.org)
Step-by-step facilitation guide
Define the pocket precisely. Avoid saying “sales is resistant.” Say, “Enterprise account managers in the Northeast region have low CRM opportunity updates and low manager confidence scores.”
Separate symptoms from causes. Symptoms include missed training, negative comments, low usage, workarounds, absenteeism from project events, or declining productivity. Causes may include lack of awareness, role impact, fear, low trust, exclusion from decisions, misaligned incentives, or lack of ability [Prosci, 2025]. (prosci.com)
Create a safe listening setting. Open with: “The goal is not to persuade you today. The goal is to understand what would prevent successful adoption and what support would make the change workable.” Psychological safety matters because people are more likely to learn and speak up when they believe interpersonal risk is safe [Edmondson, 1999]. (web.mit.edu)
Diagnose using four questions. Ask: Do people understand why the change is needed? Do they believe it is the right change? Do they believe leaders are committed and credible? Do they believe they can succeed in the new way? These questions reflect readiness dimensions found in organizational readiness research [Holt et al., 2007; Shea et al., 2014]. (journals.sagepub.com)
Match tactics to causes. If the cause is misunderstanding, use manager-led explanation, demos, and scenario-based Q&A. If the cause is low ability, add practice, coaching, floor support, and job aids. If the cause is low personal value, address workload, incentives, recognition, or role clarity. If the cause is distrust, use sponsor listening sessions and visible issue resolution. Kotter and Schlesinger’s classic guidance is that different kinds of resistance require different strategies rather than a single universal response [Kotter & Schlesinger, 1979]. (pubmed.ncbi.nlm.nih.gov)
Co-design, do not over-promise. Ask the group to rank the two or three barriers most likely to block adoption. Then agree on specific actions, owners, dates, and decision escalations.
Build the tactics into the change plan. Update the stakeholder engagement plan, manager coaching plan, training plan, sponsor plan, and adoption measurement plan. PMI notes that readiness gaps should trigger practical actions, including resourcing, timing, knowledge sharing, or risk mitigation [PMI, 2014]. (pmi.org)
Example: how this could be applied in a real change initiative
A company is rolling out a new CRM. Overall training completion is 92%, but usage data shows one sales region is updating fewer than half of required opportunities. Interviews reveal that account managers understand the system but believe it will reduce selling time and expose pipeline weaknesses. Sales managers also worry that the CRM metrics will conflict with compensation discussions.
The change manager runs a 75-minute diagnostic session with regional sales managers, respected account managers, the CRM product owner, and the sales sponsor. The group identifies three root causes: unclear performance expectations, fear of punitive reporting, and lack of mobile workflow practice. The agreed tactics are a sponsor statement on how CRM data will and will not be used, a revised manager talking guide, two mobile practice clinics, and a temporary “data quality coaching” period before compliance reporting begins. Adoption is then measured by weekly opportunity update rates, manager confidence, help desk themes, and qualitative feedback.
Roles and responsibilities
Role | Responsibility |
Change manager | Designs the diagnostic approach, facilitates sessions, synthesizes findings, and integrates tactics into the change plan. |
Sponsor | Clarifies non-negotiables, removes barriers, addresses trust issues, and reinforces why adoption matters. |
People manager | Identifies local resistance, coaches employees, provides feedback to the project team, and models support. Prosci emphasizes managers’ roles as communicators, liaisons, advocates, resistance managers, and coaches [Prosci, 2025]. (prosci.com) |
Project or product lead | Explains solution constraints, assesses feasible changes, and fixes usability or process issues. |
HR/L&D partner | Supports capability-building, role clarity, learning design, and manager enablement. |
Impacted group representatives | Surface practical barriers and test whether tactics will work in the real workflow. |
Common mistakes to avoid
The most common mistake is diagnosing resistance from a conference room instead of talking with the affected group. Another is assuming that more communication will solve every issue. Communication helps when people lack awareness, but it will not fix broken incentives, insufficient staffing, poor usability, or low trust. A third mistake is relying only on average readiness scores; averages hide pockets of risk. Finally, do not invite feedback if leaders have no intention of acting on it, because that deepens silence and distrust [CIPD, 2026]. (cipd.org)
Measures of success or adoption indicators
Measure whether the resistance pocket is shrinking and whether adoption behavior is improving. Useful indicators include readiness pulse scores, manager confidence, number and severity of unresolved concerns, training practice completion, adoption by role or location, system usage, process compliance, workaround reduction, help desk themes, quality or productivity recovery, and benefit realization. Readiness can be measured through commitment and efficacy, but the most useful dashboard combines sentiment, capability, behavior, and performance indicators [Shea et al., 2014; PMI, 2014]. (link.springer.com)
Adapt measures by phase. In design, measure participation and issue discovery. Before go-live, measure confidence, readiness gaps, and manager preparedness. After go-live, measure behavior, performance, support demand, and reinforcement.
Checklist for the change manager
Have I defined the resistance pocket specifically by group, location, role, or process?
Have I reviewed both quantitative data and direct feedback?
Have I separated symptoms from root causes?
Have I involved the people manager and sponsor?
Have I made clear what is negotiable and non-negotiable?
Have I created a safe setting for candid input?
Have I matched tactics to causes rather than defaulting to more communication?
Have I assigned owners, dates, and follow-up measures?
Have I updated the change plan and risk log?
Have I scheduled a re-check to see whether resistance is reducing?
Optional reusable worksheet
Field | Notes |
Resistance pocket | Group, role, site, process, or stakeholder segment. |
Evidence | Data points, quotes, observations, adoption metrics. |
Visible symptoms | Workarounds, low attendance, negative sentiment, delay, non-use. |
Root cause hypothesis | Awareness, value, trust, ability, capacity, incentives, culture, solution fit. |
Group input | What the impacted group says would help or block adoption. |
Tactic | Specific action matched to the root cause. |
Owner and date | Named accountable person and completion date. |
Success indicator | Metric or observation that will show the tactic is working. |
Follow-up decision | Continue, adapt, escalate, pause, or close. |
References
Prosci. Understanding Why People Resist Change. Published March 9, 2022; updated November 18, 2025. URL: https://www.prosci.com/blog/understanding-why-people-resist-change
Prosci. CLARC: The Role of People Managers in Change Management. Published June 28, 2021; updated April 24, 2025. URL: https://www.prosci.com/blog/clarc-the-role-of-people-managers-in-change-management
Project Management Institute. Change Readiness: Focusing Change Management Where It Counts. PMI White Paper, July 2014. URL: https://www.pmi.org/learning/library/change-readiness-11126
CIPD. Employee Voice. Factsheet, April 6, 2026. URL: https://www.cipd.org/en/knowledge/factsheets/voice-factsheet/
Holt, D. T., Armenakis, A. A., Feild, H. S., & Harris, S. G. Readiness for Organizational Change: The Systematic Development of a Scale. Journal of Applied Behavioral Science, 2007. URL: https://journals.sagepub.com/doi/10.1177/0021886306295295
Shea, C. M., Jacobs, S. R., Esserman, D. A., Bruce, K., & Weiner, B. J. Organizational Readiness for Implementing Change: A Psychometric Assessment of a New Measure. Implementation Science, 2014. URL: https://link.springer.com/article/10.1186/1748-5908-9-7
Kotter, J. P., & Schlesinger, L. A. Choosing Strategies for Change. Harvard Business Review, 1979. URL: https://pubmed.ncbi.nlm.nih.gov/10240501/
Edmondson, A. Psychological Safety and Learning Behavior in Work Teams. Administrative Science Quarterly, 1999. URL: https://web.mit.edu/curhan/www/docs/Articles/15341_Readings/Group_Performance/Edmondson%20Psychological%20safety.pdf