Microsoft Copilot: the change-management playbook nobody talks about
Copilot licences don't create value. Adoption, prompt hygiene and workflow redesign do.
Assistant tools are usually deployed as a licence rollout and then judged as a productivity programme. That mismatch explains most disappointing results.
Adoption follows relevance. People use the tool when it helps with a task they already do often and dislike. Identify those tasks by role before launch rather than asking everyone to find their own use case.
Prepare the content estate first. If permissions are loose, an assistant will surface documents people were never meant to read, and trust in the rollout will not recover quickly.
Train on the workflow, not the interface. A short session showing a finance analyst how to draft a variance commentary, using their own reports, beats a generic feature tour every time.
Nominate practitioners rather than champions. What changes behaviour is a respected colleague sharing a prompt that saved them an afternoon, in the team meeting, not a campaign from the centre.
Set an expectation about verification. Staff need explicit permission to check output and an obligation to do so for anything customer-facing or financially material.
Measure what you can defend. Weekly active use by role, tasks completed with assistance and time saved against a baseline are enough to make a renewal decision with confidence.
