Copilot adoption
Copilot adoption rarely fails on technology.
The licences work. The rollout is done. And still, usage stalls at summarising a meeting. Adoption is a behaviour problem, so you measure it as behaviour: at the start, along the way and in the 60 days after the certificate.
Why licences aren't a rollout
01 · The problem
Licences are a cost item until someone changes their behaviour. That's the whole case in one sentence, and it's the sentence most adoption plans skip over.
A typical programme looks like this: procurement arranges the licences, IT provisions them, there's a kick-off with a demo, and then everyone waits for usage to pick up by itself. After three months the counter shows eighty percent active users and it looks fine. Anyone who digs deeper discovers that nearly all that activity consists of a single action.
That's not surprising. Summarising meetings is the one task where Copilot explains itself: you don't have to learn anything, the button is right there, and the result is immediately usable. Every other task asks you to do something differently than you're used to, and that doesn't happen by itself, however good the tool is.
The second problem is that you can't demonstrate it. Without a baseline you don't know where people stood, so you can't show afterwards what changed. All you have is usage figures, and usage figures measure who pressed a button. For the conversation with your board that's too little, and rightly so.
That's why every programme here includes a baseline: on working day five, around five minutes per employee. Role, work context, knowledge level and self-assessment. It costs the organisation nothing technically and produces the only figure you can use later: the difference between then and now, with a remeasurement on days 40 and 60.
What you get back
Per team you see the estimated time saved and the share genuinely applying Copilot. That backs up the investment and shows which team needs to go deeper.
Measure → Train → Embed
02 · The model
Step 1
Measure
The mandatory baseline lands on working day five and takes around five minutes. It measures role, work context, knowledge level and self-assessment; that self-assessment can only lower the level. Participants never see their own level: whoever reads the label beginner starts behaving like one.
Step 2
Train
26 mandatory learning moments in three phases, over 60 working days; each day session takes a small part of the working day. The programme reorders itself based on the measurement: different sequence, different examples, different pace. Do well on a test and you get more complex cases and deeper material instead of repetition; the final test remains for everyone.
Step 3
Embed
After the certificate, reinforcement runs for another 60 days: a challenge on day seven, a refresher on day thirty, exactly in the period where adoption sticks or fades. After that, a quarterly pulse asks whether it's still being used. Without this step it fades all the same.
The six mistakes we see most
03 · From practice
01
Starting without a baseline
The most common and the most expensive. You can't fix it retroactively: once the rollout is running, the starting point is gone. Everything you measure after that is a number without a comparison.
02
One session for a mixed group
A room with five levels becomes a compromise: too slow for the front-runners, too fast for the rest. First bring everyone to level with e-learning, then run a session on whatever is left.
03
Stopping at the certificate
A certificate measures that someone finished a course, not that their behaviour changed. Without repetition in the weeks after, it fades, and then the budget bought a feeling.
04
Putting up leaderboards
A leaderboard works for two weeks and then stops. What's left is people managing the number instead of their work. That's why our dashboard shows teams, not individual rankings.
05
Leaving the data a mess
Copilot is only as good as the findability of your documents. If three versions of the same policy coexist, it picks one, and not necessarily the valid one. That's an information problem, not a training problem.
06
Involving the works council too late
Any measurement involving employees raises questions about what the employer sees. Those questions come regardless; answering them early costs one conversation, answering them late costs a rollout.
Questions about Copilot adoption
04 · Frequently asked
What is Copilot adoption exactly?
The difference between handing out licences and getting people to work differently. So you don't measure adoption by active user count but by behaviour: are people doing tasks differently than six months ago, and are they keeping it up?
Why isn't active user count a good measure?
Because someone who summarises one meeting a day counts just as heavily as someone who rebuilt their entire working week. The number rises nicely and says nothing about value. It's also the number boards are quickest to settle for.
How long does a Copilot adoption programme take?
The programme counts 26 mandatory learning moments in three phases, spread over 60 working days. A day session takes a small part of the day and falls on the participant's own working days. A habit takes about 66 days on average; that is where the 60 working days come from. After the certificate, reinforcement runs on for another 60 days.
Do you need access to our Microsoft environment?
No. We measure through the participant, so you can start tomorrow without an IT project. No fuss, just safe; the details are in our privacy statement.
What usually goes wrong?
Three things, in this order. The rollout starts without a baseline, so nobody can demonstrate afterwards what it delivered. One classroom session is given to a group spread across five levels. And after the certificate nothing happens, so it fades within two months.
Should everyone start at once, or in phases?
In phases, but not by department, by readiness. Start with the teams whose manager uses it themselves. That group produces the examples you'll use to convince the next one. A rollout starting with the most sceptical department costs twice the energy.
Read on
- The session for managers
Roll-outs rarely stick when the layer above doesn't know what it delivers.
- The plan in depth
Measure, train and embed, written out step by step.
- Licence and training cost
Two separate bills that often get mixed up, laid out side by side.
- The employer dashboard
The dashboard, the monthly email and the Excel export.
- Why embedding works
The forgetting curve, the Leitner ladder and the limit we draw around it.
- AI literacy and the obligation
Since August 2026 the same measurement doubles as your AI Act justification.
- Copilot for HR and L&D
Figures you can use to justify the rollout internally.
Start by measuring. The rest follows.
In a half-hour demo we show the baseline assessment and the dashboard on sample data. You get an answer from a person within two working days.