The all-hands said the company now had AI. Everyone had a login. A month later, a manager asked her team what they were using it for. The answers were a few private shortcuts and a lot of politeness. The official story was transformation. The actual story was a new icon.
Nobody had decided which work was supposed to change.
pick one job
A rollout worth the name picks one recurring job and redesigns that job. Not every job. One. The weekly update. The first response to a customer. The way a new hire learns the billing exceptions. Write the before and the after in plain steps. Say what the tool does in the middle, and what the person still does at the end.
If you cannot describe the after, you bought access. Say that honestly. Access is fine. It is just not a result.
A login does not change a Tuesday.
write the rule for the human part
People need to know when they are still on the hook. The tool may draft. A named person still sends. The tool may suggest a refund. A named person still approves one over a certain amount. Put that rule where the work is, not in a policy PDF from the week of launch.
Then look at that one job in thirty days. If it is not different, the rollout has not happened yet, regardless of how many seats are active.