Licences do not create habits. Teams adopt Microsoft Copilot when they see it working on their own tasks, with prompts they can reuse and someone to ask.
Here is a five-day plan. Fifteen to sixty minutes a day.
Monday: choose three tasks
Get the team together for 30 minutes and list the tasks they repeat every week. Pick three that are frequent, text-heavy and low-risk. For example: meeting recaps, first drafts of standard letters, weekly status updates.
Tuesday: write the prompts
For each task, write one prompt using the four-part structure (goal, context, source, expectations). Test it on real examples. Save the best version in Microsoft Copilot Prompt Gallery and share it with the team.
Wednesday: build one agent
Take the task with the most repeated context, such as house style or a policy, and build an agent in Agent Builder grounded in the right SharePoint folder. Test it with seven questions (see Your first agent).
Thursday: make a champion
Instead of training everyone at once, coach one enthusiastic person properly. They become the first port of call and collect questions for the team.
Friday: agree rules and measures
- Confirm the review rule: what must be checked by a person before it leaves the team.
- Agree two simple measures, such as "recaps sent within one hour of a meeting" or "first drafts started in Microsoft Copilot".
- Book a 20-minute check-in for two weeks later.
After week one
- Use the Microsoft Copilot usage reports (admin) to see adoption trends.
- Add one new task to the list every fortnight.
- Retire prompts and agents nobody uses.
Sources
Product details checked against these Microsoft pages in October 2026. Microsoft updates Microsoft Copilot frequently, so check the current page before relying on a detail.
Choose the right starting point for your organisation
Tell us who you want to train. Request dates for a private Copilot cohort or ask about a discovery conversation.
Prefer email? josh@igoe.ai