No enterprise tool can remove employee resistance to a new AI workflow on its own. The most useful approach combines practical, role-specific learning resources with manager and champion support, clear governance, employee feedback, and ongoing measurement. For Microsoft Copilot deployments, Microsoft’s adoption resources and Copilot Dashboard can support that work; Prosci ADKAR can help diagnose what people need as they move through a change. ADKAR is a framework, not software.
What tools and support should organizations use?
Think of these as parts of an adoption program, not competing products. Start with the workflow employees must change, then choose resources that help them understand, practice, and improve it.
- Adoption and learning materials: Microsoft offers Copilot adoption guidance, interactive scenarios, “Day in the Life” guides, user-engagement handouts, and skilling resources for AI leaders, champions and adoption managers, and IT administrators. These can help teams connect AI features to the work people actually do. Microsoft Copilot adoption resources
- Usage monitoring: Microsoft Learn describes the Copilot Dashboard in Viva Insights as a way to view organizational adoption and usage, including active users, retention, and usage by app, with benchmarks. Check the current feature set and licensing in your tenant before relying on it. A dashboard can reveal patterns; it does not explain by itself why a team is or is not using a workflow. Microsoft Learn: Copilot Dashboard
- A change framework: Prosci ADKAR organizes individual change around Awareness, Desire, Knowledge, Ability, and Reinforcement. Prosci places this model within a broader process of Prepare Approach, Manage Change, and Sustain Outcomes. Use it to identify missing support, not as a software purchase. Prosci ADKAR Model
- People who can help locally: Prepare managers to explain what is changing in their teams, listen to concerns, and create space to practice. Champions or ambassadors embedded in business units can provide practical help and surface friction that central training may miss. Microsoft’s guidance for agent adoption also emphasizes preparing managers and teams. Microsoft 365 Copilot adoption guidance
- Governance and trust guidance: Make the approved tools, data boundaries, security expectations, and employee responsibility for checking AI outputs explicit. Microsoft’s employee enablement pattern describes a standardized platform and bounded usage; Prosci’s AI guidance identifies trust, security, and ethical considerations as adoption concerns. Microsoft Learn: Employee AI enablement pattern Prosci: AI and change management
How can ADKAR help diagnose employee resistance?
Use the five outcomes as questions about the change, rather than treating resistance as a single attitude to overcome. An employee may support AI in principle but still lack the information, practice, or confidence needed to use a specific workflow.
| ADKAR outcome | Question to investigate | Possible support |
|---|---|---|
| Awareness | Does the employee understand why this workflow is changing? | Explain the reason for the change and what will differ in their work. |
| Desire | What concerns or incentives affect willingness to participate? | Listen to concerns and address practical impacts rather than assuming reluctance is uniform. |
| Knowledge | Does the employee know how to use the approved AI workflow? | Provide role-specific scenarios, instructions, and ongoing learning. |
| Ability | Can the employee perform the new workflow in real conditions? | Offer guided practice, manager support, and a way to resolve problems. |
| Reinforcement | What will help the employee continue using and improving the workflow? | Follow up, recognize useful practice, gather feedback, and adjust support. |
This framework is most useful when paired with feedback: if usage stalls, investigate where the change is getting stuck and adapt training or the workflow accordingly. Prosci describes change management as an ongoing process rather than a one-time launch activity. Prosci change management methodology
#1 Best Overall
What should a practical AI adoption plan include?
- Map the affected roles and workflows. Identify who will do what differently, where AI fits, and where human judgment remains necessary.
- Choose concrete scenarios. Use examples employees recognize from their own work instead of generic feature demonstrations. Microsoft’s scenario and “Day in the Life” materials can provide starting points for Copilot teams.
- Prepare managers and champions. Give them a clear explanation of the change, guidance for common questions, and a route to escalate concerns or workflow issues.
- Set boundaries before practice. Tell employees which tools are approved, what information may be used, how outputs should be checked, and where to get help.
- Train, practice, and collect feedback. Offer contextual learning and hands-on practice, then ask employees what is confusing, risky, or slowing the work down. Use the responses to improve both the workflow and the support.
- Measure adoption beyond access. Look beyond licenses or logins to active use, retention, use across relevant apps, proficiency, workflow integration, and appropriate business outcomes. Treat usage metrics as signals to investigate, not proof of value or employee sentiment.
- Refresh the program as workflows evolve. Update scenarios, governance, training, and manager guidance when AI tools, models, or agents change.
How should organizations compare enablement options?
The cited vendor materials do not provide an independent head-to-head scorecard, a universal winning product, or comparable prices. Use the following criteria to evaluate a platform or enablement program against your organization’s needs:
- Role and workflow fit: Are examples specific enough for affected employees to act on?
- Learning and onboarding: Is it easy to start, and is contextual learning available after launch?
- Governance: Does the approved path make identity, security, and data boundaries clear?
- Useful measurement: Can the organization assess active use and retention, then connect adoption signals to proficiency and relevant outcomes?
- Local support and feedback: Can managers, champions, and employees identify friction and prompt adjustments?
- Durability: Can the approach be maintained as models, agents, and workflows change?
What does the AT&T Copilot case show—and not show?
Prosci’s account of AT&T’s Microsoft 365 Copilot deployment reports more than 18,000 active users in six weeks, 96.4% sustained adoption among assigned users, and more than 200 live training sessions. The page also says the program expanded from 20,000 to 60,000 licenses and attributes the rollout approach to persona mapping, business-unit AI ambassadors, usage monitoring, training, and course correction. These are figures reported by Prosci in its 2026 case page; its publication date is not specified in the search result. They are not independently verified here, do not establish that any single element caused the outcomes, and are not a forecast for another organization. Prosci’s AT&T Copilot rollout account
Rank #2
What is the main takeaway for IT and change leaders?
Choose enablement tools for the job they perform: learning resources make new workflows concrete, managers and champions support practice, governance clarifies safe use, and measurement helps locate adoption friction. Pair those resources with a change process such as ADKAR and keep adapting the program based on employee feedback. The cited materials support this as a practical approach, but they do not prove that a particular product independently reduces resistance.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
