The hardest part of Copilot adoption isn’t the start. It’s the middle.

How do you overcome the messy middle of a Copilot launch?

It's one of the most common questions we get asked when talking to people about Microsoft 365 Copilot:

Years ago, when I worked in marketing, we had a simple rule: "Does it pass the Grandmother Test?" In other words, could you explain the idea in plain English to someone not involved in the project? If not, it probably needed more work. I still think about that now, especially when I see how many people are trying to work out what AI actually means for them in their day-to-day work. So, how would you explain Microsoft Copilot to your grandmother?

If you've been using Microsoft Copilot Chat and noticed the Library sitting in the left-hand navigation, you might be wondering what it actually does and how it's different from your regular Copilot conversations. You're not alone, so let's break it down!

You’ve invested in Microsoft Copilot. You’ve selected a group of Early Adopters. Licenses are assigned, enthusiasm is high… and then, a few weeks later, something changes. Usage slows down. Energy fades. People revert to old ways of working! If this sounds familiar, you’re not alone. Many organisations experience this exact pattern during their Copilot rollout. The good news? It’s not a failure of the tool. It’s a gap in how adoption is supported.

Stop digging. Start asking. We've all been there, searching through endless emails, scrolling through Teams chats, or trying to remember which folder that document was saved in. It's time-consuming, and frankly, a bit frustrating.

365 Copilot Hub support’s people with new ways of working. Copilot isn’t a ‘turn on and go’ AI solution, it works better when it’s a people-centric approach to build lasting behaviour change.

Have you or someone in your team opened Copilot and wondered what all those app icons actually mean?