Low Copilot adoption is rarely a training problem. It is a licence allocation and workflow problem. Give fewer people licences, each tied to three redesigned workflows, instead of giving everyone a licence and a webinar.
Short answer: Copilot gets little use when it is switched on as a feature instead of introduced as a new way of working. People do not know which tasks to use it for, managers expect nothing different, and nobody tracks what actually changes.
A familiar pattern
The licences are bought, there is a launch day, maybe a prompting webinar. Curiosity is high for a few weeks. A few months later a small group of enthusiasts use it daily, and everyone else has drifted back to how they worked before.
The pattern isn't unique to Copilot. It is what happens to almost every AI tool treated as an IT delivery.
What most Copilot advice says
Most articles on Copilot adoption come from partners selling training or adoption services. The advice is typically: train everyone, demo features in Word, Excel and Teams, teach better prompts, appoint champions.
None of that is wrong. But it assumes the problem is knowledge. Often the problem is that nobody decided what should be different about the work.
What public-sector pilots show
Umeå Municipality in Sweden has published results from its Copilot pilot. 80% of participants said they used the tool daily, and users saved an average of 85 minutes a week according to the municipality's own evaluation (Umeå kommun, in Swedish). It also noted that it did not reach its original time-saving target, that users "need to invest time to save time", and that it would explore which roles benefit most from a licence, since each licence has a cost (Umeå kommun, three lessons). Participants received onboarding, use cases, support, personal coaching and a peer network.
A Umeå University thesis on Copilot at an IT company found the opposite. Employees said they had received essentially no onboarding, learned by trial and error, and named the lack of formal introduction as a key reason the tool was underused (DiVA).
The difference is not the tool. It is the support around it.
Five reasons Copilot adoption stays low
1. Licences for everyone, purpose for no one. When everyone gets a licence at once, it is nobody's job to show what it is for.
2. Features instead of workflows. Learning that Copilot can summarise a meeting is not the same as a team deciding that meeting notes are now done that way.
3. Managers don't use it. If the manager carries on as before, so does the team.
4. Content that isn't ready. Copilot works with what is in your Microsoft 365 environment. Messy permissions and stale documents produce poor answers, and poor answers kill trust quickly.
5. The wrong metric. Many track active users. That says nothing about whether the work has changed.
How to restart Copilot adoption in six steps
1. Pause new licences
Before buying more, find out who genuinely uses it and for what.
2. Pick three workflows per role
For each role or team, which three recurring tasks should be done with Copilot? The weekly report, the meeting minutes, the first draft of a proposal. Redesign them concretely.
3. Allocate licences by workflow
People with a defined workflow get licences first. You get more value per licence and a clearer story.
4. Train on those workflows, in the team
Short sessions using the team's own documents and tasks. Follow up after two to four weeks.
5. Clean up the content
Review permissions and old files in the areas the chosen workflows rely on. Umeå listed security and privacy as its first lesson.
6. Measure changed work
Track whether the three workflows are now done with Copilot, what happened to time and quality, and what is getting in the way. Measure before and after.
It is about people
Prosci's study of 1,107 professionals found 63% of AI implementation challenges were human factors and only 16% technical (Prosci). At Lyon AM our view is that roughly 70% of a successful AI programme is about people, leadership and ways of working. Copilot is no exception.
Frequently asked questions
Why don't employees use Copilot? Usually because they don't know which tasks to use it for, managers don't expect anything different, or answers are poor because the underlying content is messy.
Should every employee get a Copilot licence? Not necessarily. Starting with roles that have clear, recurring workflows where Copilot makes a difference often delivers more value.
How long does a Copilot rollout take? It depends on the organisation, but plan for several months of support and follow-up after launch, not a single launch day.
How do you measure Copilot ROI? Measure whether defined workflows are actually done the new way, and compare time and quality against the baseline before launch.
Next step
Copilot rollout stalled? The Lyon AM AI diagnostic shows whether the problem is usage or foundations. Contact us for a restart built around the work, not the tool.
