Enablement · 11
The manager gets one sentence, not a launch mail
Tools ship. Habits do not, unless a manager asks for the habit again after the launch mail has been forgotten. For a company new to Copilot, the manager's job is not to be enthusiastic. It is to name the task, the person, and the check.
What the sentence contains
A usable sentence is specific. 'When you prepare Thursday's briefing, start in Word with Copilot, then send me what you changed.' It names the workflow, the person, and the evidence. 'Please explore Copilot' is not an ask. It cannot be followed, and it cannot be refused, so it teaches nothing. The September shelf, Home beside Cowork, does not make a vague ask any clearer.
What the manager is allowed to fear
People worry about being replaced by the draft, about being blamed for a wrong file, and about looking slow if they check the output. Those worries belong in the conversation. FrontierOrg, a fiction, uses Prosci's ADKAR steps and the ILO's view that exposure more often changes a job than it removes it. That story is not yours, and not a reason to announce losses.
Reinforcement is the week after
The launch is not the lesson. The lesson is whether the manager asked again, and whether the person could do the task without the trainer in the room. If the answer is no, the rollout is still in week one, whatever the newsletter says.
Monday
Send each manager one sentence for one named person and one named task. Ask them to use it in a one-to-one this week and reply with what the person changed in the file.
What will the manager say on Thursday if the file comes back unchecked?
Sources: Microsoft blog, 25 September 2026, Introducing the new Copilot (opens in a new tab). Prosci, The ADKAR model (opens in a new tab). ILO, Generative AI and jobs: a 2025 update (opens in a new tab).
Where this note mentions FrontierOrg, that is a fictional method for rehearsing a decision. It is not a company, not a client, and not a case study.