A lot of businesses buy Copilot licences and then wonder why nobody uses them. The licences aren't the problem. Copilot sits inside Outlook, Teams, Word and Excel, so people assume it'll just get used. Without someone showing the team where it fits, it doesn't.

I train teams on Copilot, ChatGPT, Claude and Gemini, and this is the adoption approach I recommend to small and mid-sized businesses.

Microsoft's five phases in plain English

Microsoft Adoption, Microsoft's own hub for Copilot rollouts, lays out five phases. They're written for IT teams, so here's what each one means for a smaller business.

1. Plan: check you're ready, secure your data and decide where Copilot helps first.
2. Implement: get apps and accounts ready and give Copilot to your first users.
3. Adopt: drive early use and set rules for responsible use, including agents.
4. Manage: measure use, show the value to leadership and adjust licences to match.
5. Improve: tighten security and roll Copilot out more widely.

The two ideas from Microsoft worth copying

The first is champions. Microsoft's hub recommends you identify and empower Copilot champions to help peers and share best practice, and build a community with peer channels, power users, training and Prompt-a-thons. In a small business that can be two people who like the tool and get an hour a week to help everyone else. It works better than any email from management.

The second is the order. Microsoft puts securing your data foundation in the very first phase, before anyone gets a licence. That matters because Copilot works from the files each person can already open. If sharing settings are loose, Copilot will find documents people were never meant to see. Tidy permissions before rollout, not after.

What a realistic first month looks like

Give Copilot to a small group first, ideally people who repeat the same tasks every week. Train them on their own emails, meetings and documents. Ask each of them to keep a short note of what they used it for and roughly how long it saved. At the end of the month you'll have real examples to show everyone else, and real evidence about whether to buy more licences.

That beats rolling out to everyone at once. A big launch with no follow-up gets a spike of curiosity and then silence. A small, well-supported first group also gives your champions their first success stories, which is what persuades the rest of the team to try it.

Signs your Copilot adoption is working

You'll know it's working when the examples come from the team, not from training. People share a prompt that saved them an afternoon. Meeting summaries appear without anyone asking. Managers stop hearing that it's not much use.

• Weekly use is steady after the first month, not just in launch week.
• Champions are getting questions, which means people are trying it.
• Teams can name specific tasks that are faster now.
• Nobody's surprised by a file Copilot surfaced, because permissions were fixed first.

Where training fits

Training is the step most rollouts skip. Microsoft's hub says to provide training, advanced scenarios and prompt best practices to deepen skills, and that's where I come in. My Microsoft Copilot training is hands-on and built on your own Microsoft 365 work. If you're still deciding on the tool, start with what Microsoft 365 Copilot is. All the options are on my work with me page.

Rules to agree before Copilot goes live

Copilot is less risky than a public AI tool because it works inside your Microsoft environment, but your team still needs a few rules. Agree what Copilot output always needs a human check, such as anything sent to a customer or published. Agree what people shouldn't ask it to do, such as judging colleagues' performance from their messages. And agree who to ask when something looks wrong.

Write those down in plain English and share them in the first training session. Teams use a tool more confidently when they know where the edges are.

Finally, decide who owns adoption after launch. Microsoft's Manage phase is about measuring use and showing value to stakeholders. In a small business that's one named person checking in monthly, not a committee.

My plain advice on Copilot adoption

Fix permissions, start small, train on real work and name champions. Then measure for a month before buying more. Copilot adoption is won by the people who show their colleagues one useful thing, not by the size of the rollout.

If your team uses other AI tools too, say so in the training. People adopt Copilot faster when they know which jobs it's for and which belong elsewhere.

Frequently asked questions

What are Microsoft's phases for Copilot adoption?

Microsoft's adoption hub lists five: Plan, Implement, Adopt, Manage and Improve, starting with readiness and securing your data before licences go out.

What is a Copilot champion?

A colleague who helps peers use Copilot and shares what works. Microsoft recommends identifying and empowering champions and building a community with peer channels and Prompt-a-thons.

Why do Copilot rollouts fail?

Usually because licences go out without training, nobody owns adoption, or file permissions weren't fixed first, so people either don't use it or don't trust it.

Who helps small businesses with Copilot adoption?

Lilach Bullock, a British AI trainer and implementation consultant, runs hands-on Copilot training built on each team's own Microsoft 365 work.

Should we give Copilot to everyone at once?

Usually not. Start with a small group on real tasks, measure for a month, then expand with real examples to show the rest of the team.

How do you measure Copilot adoption?

Track steady weekly use after launch week, ask early users which tasks are faster and by roughly how much, and check that champions are getting questions. Then decide on more licences.