4.2.1. Adoption Barriers and Champions Programs
💡 First Principle: Adoption barriers fall into three categories: Capability (can't use it), Motivation (won't use it), and Opportunity (no chance to use it). Different barriers require different interventions—training for capability, success stories for motivation, protected time for opportunity. Diagnosing the barrier correctly is essential.
Understanding adoption barriers:
| Barrier | Symptom | Intervention |
|---|---|---|
| Capability | "I don't know how to use it" | Training, documentation, hands-on practice |
| Motivation | "I don't see why I should use it" | Success stories, ROI demonstration, quick wins |
| Opportunity | "I don't have time to use it" | Protected learning time, workflow integration |
AI Champions programs:
AI champions are employees who advocate for AI adoption within their teams. They're not IT staff—they're peers who demonstrate value and provide support. Choose them for enthusiasm, communication skills, and peer respect—not technical depth or seniority.
Effective champions programs include:
- Selecting enthusiastic early adopters from each department
- Providing champions with advanced training and early access
- Creating forums for champions to share successes and challenges
- Recognizing and rewarding champion contributions
Diagnosing and sustaining adoption:
- Diagnose from what non-users say. If people who try the tool keep using it, Capability isn't the blocker; "no time / no natural moment in my day" points to Opportunity, "I don't see what it does for me" to Motivation.
- Map barriers before launch. Plan training, use cases, and protected time from day one instead of waiting for post-launch usage data to reveal confusion.
- Address job-security fears honestly. Acknowledge the concern, explain how AI augments roles, and share concrete internal examples—dismissing it as "fear of change" deepens resistance.
- Watch for change fatigue. Teams worn out by back-to-back changes disengage from any new initiative; pace and sequence the rollout.
- Celebrate early wins. Recognizing pilot successes builds peer momentum before productivity targets are reached.
- Measure outcomes, not access. Track active usage, productivity gains, and user satisfaction (for example with the Copilot Dashboard in Viva Insights)—not licenses or training attendance.
⚠️ Exam Trap: When a question describes low adoption, identify the barrier type before selecting the intervention. "Users don't have time" = Opportunity barrier (not training). "Users don't see value" = Motivation barrier (not documentation).
Reflection Question: Six months after deploying Microsoft Copilot (formerly Microsoft 365 Copilot), usage data shows that employees who try Copilot use it regularly, but most employees haven't tried it at all. What type of barrier is this, and what would you recommend?
