The pattern is consistent enough now that we use it as a discovery-call question. Tell us about the last technology rollout where adoption surprised you on the upside. The good answers all share one feature.
Someone, before launch, wrote down what the technology was supposed to make easier, by role.
Not the feature list. The day. The Tuesday morning of an analyst. The Wednesday afternoon of a development director. The standing meeting a controller used to dread.
The gap most rollouts skip
The typical Copilot rollout we are asked to rescue went something like this. Licenses were purchased. A kickoff call happened. Two training sessions were offered, of which 18% of license holders attended at least one. A Teams channel was created. Three months later, usage data showed that 11% of license holders had opened Copilot in the last seven days.
Nothing went wrong, exactly. The licenses worked. The training was professional. The Teams channel had announcements. But no one had ever answered the question Copilot is supposed to answer. Which is: what does a good day with this tool look like for the person whose seat it is on.
What writing it down changes
Writing it down forces three decisions that the average rollout defers indefinitely.
It forces a decision about which roles get licenses first. The answer is rarely “everyone in the leadership team.” It is more often “the twelve people whose Tuesday mornings look most like the day we just described.”
It forces a decision about what training looks like. A two-hour overview becomes a thirty-minute role-specific session about the three workflows that show up in the written-down day.
It forces a decision about what success means. Twelve weeks in, you can hold the written-down day next to the actual day and have a conversation about which parts moved.
The organizations whose Copilot rollouts are humming a year later did some version of this. The ones quietly unwinding did not.