Pilots almost always work. You pick the twelve most enthusiastic people in the building, hand them a tool they have been reading about for a year, and they use it. Of course they do.
Month two is different. The pilot group has answered the novelty question and moved on. The wider rollout has landed on people who did not ask for this. Somebody has produced a document with a confident error in it and nobody is sure whose problem that is. And the person driving the whole thing has a day job.
Three things kill it, and none of them are technical.
An unnamed owner. "The team" owns week six, which means nobody does, which means week six does not happen. Put a human name in the cell.
No answer to the sign-off question. When Copilot summarises a contract wrongly, who is accountable? If the answer is "the user should check," that is not a policy, it is a hope. Write the actual role that carries it.
Measuring licences instead of tasks. Assigned licences go up and nothing changes. Pick three tasks that should get faster, measure those, and be willing to hear that one of them did not.
You can act on all three today without buying anything. If you would rather not build the scaffolding yourself, the Kit is the scaffolding: 12 weeks, owner column, governance checklist, comms for each phase. $97, and The AI Champion's Playbook is included free until Tuesday.
Mathieu