Copilot Adoption: 80% or 30%?
It's Not the Product
While I write about the latest and greatest, and my bubble gets excited about Edit in Copilot becoming generally available and how to optimize the daily work even more with Copilot Cowork, most people still struggle to even use AI once a day.
When they do use it, it’s usually to find information about the tenant. Which is great, right? But there’s still no AI mindset. There’s no natural behaviour to turn on the transcript before a meeting starts. They don’t think about connecting working steps with Copilot either.
At the same time, most organizations buying Copilot licenses today still believe one thing that’s wrong: that their people will figure Copilot out on their own. The argument I hear:
We didn’t train people on Teams either, why should we train them on Copilot?
PS: those are usually the same organizations that have an absolute mess inside Teams today, because there was no clear guidance back in 2021 when they rolled it out just before the first lockdown.
That belief “they’ll figure it out” is the single biggest reason Copilot adoption stalls.
The Hard Numbers
Let me give you the data first. Recon Analytics surveyed 150,000+ U.S. enterprise users and found Microsoft Copilot’s workplace conversion rate sits at 35.8%. (at least in the US) That means only one in three people with a paid license actively uses it. Microsoft has 15 million paid Copilot seats as of Q2 FY2026, representing about 3.3% of their 450 million commercial M365 installed base.
Now combine these numbers with what I see in client projects every week. The trend is encouraging on one side: more and more organizations are ready to rollout Copilot for their organization. Many of them run real adoption programs. In Switzerland, a lot of those organizations are our Campana & Schott customers, and the difference shows. They reach +75% daily active usage.
But there are still too many organizations doing it wrong. They buy the licenses, send the email, run one webinar, and then wonder why nothing happens. Three months later they sit at 25-30% usage and start questioning the investment.
Same Copilot features, same price, different outcomes
The question for every manager reading this: which group is your organization in?
The Myth That Breaks Adoption
Here’s what I hear from employees (not managers) so many times:
“We’ve got Copilot, but I have no clue how to use it. And I have no time to find out. So I stick to my way of working.”
Three months later the dashboard shows 25% active users. Leadership discuss it internally: “Feature x is not working, that’s a no go! Have you seen the new model xyz?”
That’s the wrong discussion. The right discussion is: “How can we connect Copilot to the daily work?”
Copilot is not Outlook. Outlook works the way email worked since 1995, you learn it once, you know it forever. Copilot or AI in general is something different: it’s a tool that requires new habits, new mental models, and new workflows. And these steps you have to rerun it every second months, because speed of innovation is that fast.
You don’t learn Copilot by opening it and staring at the prompt box. You learn it when you have your aha moments, when you suddenly realize why this matters for your daily work. When you see Copilot turn 40 minutes of meeting prep into 5 minutes. When it pulls together information from three different SharePoint sites, combined with you meeting transcript and the email you wrote 2 weeks ago, that you would have spent half a day searching for. Those moments don’t happen by accident. They happen because someone showed you the right use case at the right time.
That process doesn’t happen on its own. It happens when an organization builds it.
🫵🏼 What was you’re aha-moment with Copilot? Let me know in the comments
What the 80% Do Differently
I’ve seen a pattern across customer engagements where Copilot adoption actually works. It’s not magic, but it’s investment in the right places.
They start with 10 use cases, not 100 features. They pick the ten workflows that matter most for their business: sales meeting prep, monthly reporting, proposal writing, customer email responses and they build training around those specific workflows.
Nobody learns “Copilot.” Everyone learns “how I use Copilot for my job.”
They make leaders visible users. If the CEO doesn’t touch Copilot, adoption dies at middle management. Top-adoption organizations have executives who share their prompts, their wins, their mistakes. It cascades down.
They train in context, not in classrooms. Generic Copilot training sessions only works in the ramp up. Create day in a life scenarios for your individual roles. Connect features with jobs to be done.
What works is embedding adoption in existing team rituals. someone demos a use case in the weekly team meeting, the sales team has a 20-minute “Copilot for pipeline review” session, HR shows how they use it for interview prep.
They create internal champions. Every team has one person who becomes the “Copilot champion.” A colleague who figured out three workflows and shares them. That peer-to-peer delivers so much value.
The common thread: they treat Copilot adoption as a program, not a product launch.
What the 30% Believe it’s Right to Do
The other side of this pattern is equally consistent. Organizations below the 30% adoption line share a few characteristics.
They confuse access with adoption. “We gave everyone a license, so we’ve done our part.” Licenses are distribution, but adoption is behavior change. Those aren’t the same thing.
They expect one training session to work. A one-hour webinar on “Introduction to Copilot” is not training. It’s awareness. People need repetition, real examples from their own work, and support when they get stuck.
They see: adoption program = training. Adoption needs so much more and yes, training sessions are one part of it, but not the only one. Start with why, build the story, think about communication, communities and how to anchor it. It also needs a proper transition to line, to ensure the new features reaches the organization.
Their leaders don’t use it. This is the killer. I can tell within 10 minutes of a leadership meeting whether the organization will reach 70%+ adoption. If the executive team shows up and only one person has actually used Copilot for a real task in the last week, that organization will most likely stall at 30%.
They never define what “good” looks like. “Saves time” is not a success metric. “Sales reps use Copilot for every client meeting prep, measured in the CRM” is a success metric. Without clarity on what adoption should produce, there’s nothing to measure and nothing to improve.
What This Means for you
If you lead a team, a department, or an organization with Copilot licenses, the honest question is this: are you running a program, or are you running a distribution?
If it’s a distribution: You already spent money for the license, so do it right! You bought the licenses, sent the email, hoped for the best your adoption is probably low. Your license spend is mostly waste. And every quarter that passes, your competitive disadvantage compounds.
If it’s a program: Congrats! With defined use cases, leadership commitment, champion networks, regular measurement, you have a realistic path to 70%+ adoption. That’s where the advantages lives.
The product is the same for everyone. The outcome is not.
On a Personal Note
My goal with this newsletter is always the same: connect the dots between what’s new, what’s next, and what works in practice. Frontier topics like Cowork and Custom Skills matter, but only if the basics are in place. And the basics only stick if the organization takes adoption seriously.
That’s why I’m writing this one for decision makers specifically. If you’re responsible for Copilot in your organization, whether as CIO, HR lead, transformation officer, or business leader, you’re the one who decides which side of the 80/30 split your company ends up on.
If you’re interesting how this works in practice, write me and we can talk.
After hundreds of conversations with customers, my honest take: the companies that will win with AI aren’t the ones with the biggest budget or the fanciest tech stack. They’re the ones who treat Copilot as something that needs to be learned, not just installed.