Copilot adoption is an operating-system problem.

The default response to flat Copilot usage is a training program. Training helps the people who were already going to use it. It does not move the seat that was assigned to someone whose work never presents a moment to use it, and it does not tell you which of those two you are looking at.

Adoption is an operating-system problem in the plain sense: it depends on where the seats sit, what the day looks like for the person holding one, and whether anyone is counting. Three things move it.

Seats where readiness exists. Reclaim the cold seats and put them where the work has a Copilot-shaped moment every day. The reclaim pays for the move — unused licenses fund the activated ones.

A workflow, not a feature. An agent that drafts the Monday summary inside the document the person already opens beats a portal they must remember to visit. The work gets done where the work happens.

A proof cycle. Take the baseline, nudge one group, leave a control group untouched, and read the difference next month. If the lift is not there, the program changes, not the story.

Run that loop monthly and adoption stops being a training metric and becomes an operating one — with an owner, a number and a next move.

Published 14 September 2026 · All insights