Executive Sponsorship
Without a real sponsor, adoption stalls. The sponsor communicates the “why”, funds the project, and removes blockers when a regional VP refuses to deprecate her spreadsheet. The signature test: does the sponsor show up at the kickoff and the 90-day review without being chased? A CRO who delegates the rollout to a director and never speaks to it in QBRs has effectively withdrawn sponsorship even if the org chart still names them. Decline projects whose sponsor will not commit to a recurring 30-minute monthly slot for the first two quarters; the data from Prosci’s 2025 benchmark shows projects with active sponsorship are six times more likely to meet objectives.
Stakeholder Map
Identify champions and skeptics early because both are valuable. Champions amplify; skeptics surface the objections your steering committee has not heard. Use a 2x2 of influence vs support, refresh it every six weeks, and assign an owner to every high-influence skeptic. A common mistake is treating the loudest skeptic as the enemy — they are usually the future champion if their objection is taken seriously. Run a 30-minute “tell me why this will fail” session per region; the Salesforce or Dynamics 365 admin who runs that session learns more than any consultant deck reveals.
Communication
Over-communicate in month one through email, all-hands, and team standups. Repeat the “why” because adults need to hear a message seven times before it lands, per the standard marketing rule that applies equally to internal change. Address rumors within 24 hours: the rumor that “this CRM will be used to track activity for layoffs” has killed more rollouts than feature gaps. A simple weekly two-paragraph email from the sponsor — what shipped, what is next, one user quote — beats a polished newsletter that goes out monthly.
Training
Role-specific, scenario-based, just-in-time training beats a one-shot bootcamp. Build a path per persona: an SDR needs lead routing and cadence enrollment; a CSM needs renewal forecasting; a sales manager needs pipeline inspection views. Combine a 20-minute video, a live 45-minute hands-on, and a one-page PDF reference per scenario. WalkMe, Spekit, or Pendo in-app guides catch the moments when a user is about to abandon a flow. Plan for a refresher in week 6 — the Ebbinghaus forgetting curve guarantees that 70% of one-shot training is gone by then.
Reinforcement
Adoption is fragile in the first 90 days. Manager check-ins, usage dashboards reviewed in 1:1s, and incentives tied to milestones (logged calls, opportunity hygiene, NPS for internal users) keep momentum. Publicize wins with names attached — “Marta closed her first deal using Agentforce next-best-action” beats anonymized stats. Tie a small portion of the variable comp plan to CRM hygiene metrics for the first two quarters, then sunset it once habits are formed.
Common Failure Modes
The dominant failures are predictable: a sponsor who disappears after kickoff, training delivered before the system is configured for the user’s actual workflow, and a “go-live” that is really a “throw it over the wall” because the project team disbands the day after launch. Watch for the silent rebellion — a region that politely attends training then continues using the legacy tool. Pull adoption telemetry weekly and call the regional manager the moment the curve diverges.
What to do this week
Schedule a 30-minute working session with your sponsor to write the one-paragraph “why” in their voice. If they cannot give you 30 minutes, escalate or pause the project. Then publish a stakeholder map with named owners for every high-influence skeptic before the next steering committee.
