The problem this solves
Rollout plans usually model logistics, not people: licenses, training dates, go-live. Then reality arrives: the veteran rep who quietly tells the team the old way was fine, the manager who nods in meetings and deprioritizes the change after, the team that adopted the last three tools and is out of patience for a fourth. Resistance is rarely loud; it is passive, distributed, and discovered too late, after the initiative has already been declared a success in a steering deck.
How we work
We map the human terrain before rollout. Through structured interviews and a readiness survey across affected teams, we identify where genuine support lives, where resistance sits and what drives it: workload fear, past rollout fatigue, loss of status or autonomy, or plain disagreement with the direction, which is sometimes well founded and worth hearing.
We pay particular attention to informal influence: the people whose opinion moves the team regardless of their title. Winning them changes adoption curves; ignoring them explains most stalled rollouts.
The deliverable is a stakeholder map with support, neutrality, and resistance segments, an honest register of resistance drivers, and an engagement plan per segment: who needs involvement, who needs evidence, who needs their concerns fixed rather than messaged at. It plugs directly into change communication planning and rollout sequencing.
Deliverables
- Stakeholder map across affected teams with support and resistance segments
- Resistance driver register based on interviews, not assumptions
- Informal influence map identifying who actually moves opinion
- Adoption risk assessment per team with likely stall points
- Segment-by-segment engagement recommendations for the rollout
What buyers ask before scoping.
How do you get people to admit they will resist a change?
By not asking that question. We ask about their work, past rollouts, and what would make this one fail; resistance surfaces in those answers reliably. Interviews are confidential, findings are reported by segment rather than by name, and we say so upfront. People are strikingly honest when honesty is safe.
How is this different from the Leadership Alignment & Sponsorship Assessment?
That assessment covers the top: whether executives agree and will sponsor. This one covers everyone the change actually lands on: managers and teams whose daily behaviour decides adoption. A change can have perfect sponsorship and still die in the middle layer; the two assessments look at different failure modes and pair well.
When in the project should we run this?
After direction is set, before rollout planning is locked. The findings should shape sequencing, pilot group selection, and communication, which requires them to arrive while those things can still change. Running it after go-live is possible but converts it from prevention into diagnosis of an adoption problem you already have.
Related modules
Role, Process & Accountability Assessment
Role, Process & Accountability Assessment is a diagnostic engagement that examines whether roles, processes, ...
Change Communication & Enablement Assessment
Change Communication & Enablement Assessment is a diagnostic engagement that examines how your organization ...
Leadership Alignment & Sponsorship Assessment
Leadership Alignment & Sponsorship Assessment is a diagnostic engagement that tests whether your leadership ...
Sounds like your situation?
30 minutes, your calendar, no slide deck. We tell you honestly whether this module fits.
Book discovery call