The Stalled Rollout

A rollout that has slowed to near-zero adoption three months in has not failed yet. It has reached a decision point: diagnose and intervene, or let it die quietly and become another cautionary tale.

Let me be clear: there is always a blocking stakeholder. Rollouts do not stall randomly. They stall because a specific person, with a specific resistance type, in a specific position of organizational influence, has made a specific set of decisions that have accumulated into zero forward movement. Find the person. Identify the type. Design the targeted intervention.

1. 1. Identify the Blocking Stakeholder Look for the high-influence stakeholder whose adoption metrics diverge from their verbal posture. Interview the champions — who do they encounter in conversations about the initiative that creates friction? Map where adoption stops in the org chart: if an entire department is at near-zero adoption and the department head is at near-zero, start there.
2. 2. Identify the Real Resistance Type Apply the diagnostic framework from Lesson 2. Does the concern shift when addressed? Is it specific or atmospheric? Is it timed to strategic moments? Does the resistance propagate through their influence network? Identify the type before designing the intervention.
3. 3. Design the Targeted Intervention Apply the intervention framework for the identified resistance type. For Identity Resistance: role reframing. For Authority Erosion: new authority structure. For Competence Anxiety: private training and structured first success. For Legitimate Concern: co-design the solution. Do not apply a generic "more communication" intervention to a specific resistance type.
4. 4. Restart with a Phase Gate After the intervention, do not simply continue the stalled rollout. Treat the post-intervention restart as a new phase with explicit gate criteria. What must be true before the rollout resumes? Define the criteria, meet them, and document the restart. The organization needs to see that the previous stall was diagnosed and corrected — not that the rollout just started moving again for unclear reasons.