Time and time again, we hear from clients that they’ve rolled out Microsoft 365 Co-Pilot licences across their organisation, but they’re unsure whether they’re getting the benefit they expected.
In a large business, this isn’t a trivial investment. At £30 per user per month, rolling it out to a team of 1,000 employees means you're spending £30,000 per month — £360,000 a year.
It’s a serious commitment.
The potential, however, is real. Studies suggest you can unlock 2–4 hours of time saved per person per week — but only if people actually know how to use it, and more importantly, how to apply it within the flow of their work.
I've personally leaned into the use of AI in my daily work — but I know that doesn’t represent everyone. People are at different stages of the change curve. Some are excited, some cautious, some overwhelmed. Your rollout must reflect that. Not everyone needs the same training or use cases. Segment your audience and meet them where they are.
Don’t assume people will work out how to use Co-Pilot on their own. Curate a set of standard use cases for each function or role, alongside prompts that get results. Go further by identifying which use cases should be leveraged department-wide, and build these directly into workflows using Co-Pilot Studio.
Co-Pilot is only as good as the data it has access to. Audit where your information is stored. Are permissions right? Are Teams and SharePoint sites structured logically? Is your knowledge base accessible and up to date? Poor data = poor answers.
Prompting is a skill. It’s not just about asking the right question, but understanding prompt chaining — how to iterate, build on answers, and think in systems. Most people don’t need a feature tour; they need a mindset shift in how to work with a digital assistant.
Create light governance that enables teams to develop, share, and re-use effective Co-Pilot use cases. Track what’s working. Encourage teams to propose their own prompts and use cases, then socialise the ones that can scale across the business.
This is key: take a process-centric approach, not a tool-centric one. Map where Co-Pilot fits into your current workflows, from preparing for a client meeting to summarising Teams threads or building a project plan. Co-Pilot isn’t just for shortcuts — it can fundamentally reshape how work flows.
Co-Pilot isn’t magic, and it’s not always right. Set realistic expectations early — it's a productivity partner, not a replacement for critical thinking. Use bite-sized training to reinforce this message, and highlight both its strengths and limitations.
Make Co-Pilot part of onboarding, team meetings, and even personal development plans. Encourage teams to challenge each other: “Could we have done this faster or better using Co-Pilot?” This embeds a culture of continuous improvement — and AI adoption becomes second nature.
Identify Co-Pilot Champions in each department who can lead by example, support others, and share what’s working. One organisation we came across ran a brilliant “Prompt of the Week” campaign. It created a buzz and got people experimenting. Recognise and celebrate those who lean in.
Build a comms strategy that regularly shares success stories, new prompt ideas, and usage stats. Highlight the time saved, the creative breakthroughs, and the tasks Co-Pilot is now handling. Storytelling is your biggest lever for cultural change.
The licence fee is fixed — but the value you get from it isn’t. Co-Pilot can fundamentally change how your teams work, collaborate, and think. But that only happens with the right mix of enablement, structure, and culture.
Don't just deploy it. Operationalise it.
If you’d like help mapping out high-value use cases, training your teams, or embedding Co-Pilot into your workflows, we’d love to talk.
© Hudson & Hayes | Privacy policy
Website by Polar
