Notes from the field · Jul 24
Not a vague sense that "adoption is stalling." The actual 2026 numbers, so you know if your team's experience is normal, and what it's really costing you.
Only about 35.8% of employees with Copilot access use it. Rollouts tend to stall near 20% weekly seat usage after the first few months, no matter how strong the initial rollout push was. This isn't a rare failure case, it's the median outcome.
44.2% of people who stop using Copilot cite distrust of its answers as the main reason, not lack of time or lack of training. They tried it, didn't trust what it gave back, and quietly went back to doing the work by hand.
The cost isn't abstract either. A 1,000-person organization sitting at a typical 20% adoption rate is paying for roughly $240,000 a year in licenses nobody uses. Scale that math to your own headcount and it stops being a soft "engagement" problem and starts being a line item.
Across the research, the pattern is consistent: it isn't a product failure, it's a change-management gap. People get access, try it once or twice on a task it wasn't well suited for, don't build a habit around it, and never come back. Nobody showed them the handful of real workflows where it actually saves time, so the license just sits there.
If your numbers look like the ones above, that isn't a sign your team is behind. It's the industry norm. What separates the teams that fix it isn't a better tool, it's someone sitting with the team, mapping the actual workflows, and building the habit deliberately instead of hoping a license unlocks it on its own. That's the entire job of an Assessment: find out whether your stall is the tool, the training, or the workflow, and fix the actual cause instead of guessing.