Avoid these 3 mistakes when implementing Copilot

By Bo Fischer Carlsen

Read Bo Fischer Carlsens first blog post about Copilot. This blog post is the first in a series of three blog posts about Microsoft Copilot.
Copilot is in its first year, and many Danish companies have been busy implementing various versions. However, as with many major change processes, it has not been without its challenges. Copilot increases business efficiency and quality and removes unnecessarily heavy tasks from employees, but it's not without its challenges. Here are three mistakes to avoid when implementing Copilot in your organization.

Many people underestimate users' training needs. Copilot and generative AI are new technologies, and without proper training, users often don't know where to start or how to best use the tool in their daily work. Copilot is rapidly evolving and adding new functionality, which can confuse.

Solution: Create dedicated training sessions that show how Copilot can be used in recognizable workflows in users' everyday work. It's also vital to explain Copilot's limitations so that users have realistic expectations.
At Delegate, we also find that users often need extra support. That's why we always set up open calls with users where they can share their experiences, frustrations, or areas where they think Copilot can help but are struggling to get started.

1. Underestimating the need for training

Many people expect that you can centrally develop company-specific use cases that fit all employees, and you're good to go. However, this is far from reality. Copilot for Microsoft 365 is primarily designed to support personal productivity and assistance, making it impossible to generalize. Users are not the same; they work differently and have different backgrounds. Suppose the implementation is not customized to the individual needs of users. In that case, we encounter frustration and a perception that Copilot cannot help them because they feel their tasks are too unique to be supported by AI.

Solution: We need to personalize our approach. While a prompt catalog can inspire users on how to get started, the Copilot rollout should be seen more as a change management exercise. We need to provide users with:

  • Tools, knowledge, and methods to integrate this new tool into their daily work
  • A network of other users who are on the same journey with Copilot
  • The courage and opportunity to take an experimental and playful approach to Copilot
2. Believing in a "one size fits all" model

I've been there, and many of my colleagues and customers I talk to have been there, too. When you first license Copilot, you think it's all about Copilot in Office applications like Word, Teams, and Outlook. But you're missing out on an excellent opportunity to utilize Copilot fully. Copilot Chat gives users an easy entry point to generative AI. For example, it can pull information from different documents and emails and give you a comprehensive overview so you don't have to go through everything manually.

Solution: Copilot Chat should be central to training and onboarding. It's the ideal starter tool to introduce users to a workday with generative AI.

3. Underestimating Copilot Chat

Copilot for Microsoft 365 can transform how we work, but only if we avoid these common mistakes. By ensuring good training, adapting to individual user needs, and centering your adoption around Copilot Chat, you can maximize the benefits of Copilot!

Is your organization ready to take the next step?

What's next?

About the author

Bo Fischer Carlsen, Managing Consultant
Bo Fischer Carlsen is a Modern Workplace Lead at Delegate, with years of experience in Microsoft 365, SharePoint, and related technologies. He is driving Delegate's Copilot Adoption Framework, to ensure success in with Copilot. He has expertise in various areas of Microsoft 365 and Modern Workplace, gained through his industry and consulting experience.
en_GBEnglish