What does a rollout actually consist of?

Explaining what the tool is for, saying plainly what people may use it on, showing the specific task their team does rather than the feature list, and naming who to ask. The access part is administration and takes an afternoon; these four are the work and they take weeks.

Because each group produces people who can help the next, problems surface while they are cheap, and the support load stays survivable. Rolling out to everyone at once puts every question in the same week at whoever set it up, which slows the whole thing down while looking faster on the plan.

What gets missed most often?

Saying clearly what material is permitted. People who are unsure quietly do not use the tool rather than asking, because asking feels like inviting a refusal. That single unanswered question suppresses more use than any gap in training, and it costs nothing to answer.

Glossary

Rollout

A rollout is the work of taking a tool from a group that has proved it to everybody who should have it, which is mostly communication and training rather than installation.

In plain terms

Giving everybody access is usually the easy part and takes an administrator an afternoon. The work is explaining what the tool is for, what people are allowed to put into it, who to ask when it behaves oddly, and why anybody should change a method that currently works for them. Rollouts that treat the afternoon as the job produce a lot of licences and very little use.

Why it matters

Because the technical simplicity is misleading and it sets the wrong expectations about effort. Access is instant, so a rollout gets planned as an announcement, and the questions people actually have go unanswered: whether customer material is permitted, whether their manager expects this now, what happens if the output is wrong. Unanswered, those questions do not become objections, they become quiet non-use.

How it works

Staged beats simultaneous almost always, and not for technical reasons. A group at a time gives you people who can help the next group, surfaces the confusing parts while they are still cheap to fix, and keeps the support load survivable. Everybody at once means every question arrives in the same week, at whoever set it up, who is now the bottleneck.

The permission question is the one that stops people and it is rarely on the agenda. Whether this may be used for customer material, for anything confidential, for work that goes outside: staff who are unsure default to not using it, and they do not raise it because asking feels like inviting a no. Saying plainly what is allowed removes more friction than any amount of feature training.

Training on the work beats training on the tool. A session demonstrating features is forgotten by the time the relevant task appears; fifteen minutes on the specific thing this team does every week, with their material, is remembered because it maps onto something real. The second is also harder to prepare, which is why the first is what usually gets delivered.

People who have already made it work are the most effective part of a rollout and the most often unused. A colleague who does the same job and has adapted their method carries more weight than any central communication, and the cost of asking a few of them to help is trivial next to the effect.

Where the effort is assumed to be, and where it is

What makes the left-hand plan so persistent is that every step in it is genuinely easy, and easy steps are what get scheduled. Provisioning is an administrator's afternoon, an announcement is an email, and a training session is an hour in a calendar. The right-hand version asks for judgement about who goes first, a decision somebody has to make about permitted use, and preparation specific to each team's work, none of which can be delegated to whoever holds the administration console. That asymmetry is the whole reason rollouts default to the left column, and it is also why the outcome is so predictable: the organisation completes every task it set itself and still ends up with people who have access to something they have not been given a reason to use.

Seen in the wild

Moving a team already using an assistant on individual accounts onto an administered one, which is a rollout and a policy fix at once.
ChatGPT
Introducing search department by department, as each department's systems are connected rather than all at once.
Glean
Rolling out AI inside a workspace people already open daily, where the training is about the work rather than about finding the tool.
Notion AI

Common misconceptions

People assume

A rollout is finished when everybody has access.

In fact

That is the start of it. Access is an afternoon's administration; the rollout is the weeks afterwards in which people find out what it is for, what they may use it on, and who to ask. Declaring completion at the access point is what produces a full licence count and an empty usage report.

People assume

Everybody at once is fairer and faster.

In fact

It concentrates every question into one week and leaves nobody who has been through it to help. Staged is slower on paper and finishes sooner in practice, because each group produces people who can support the next one and problems get fixed while they are still small.

Questions

What does a rollout actually consist of?: Explaining what the tool is for, saying plainly what people may use it on, showing the specific task their team does rather than the feature list, and naming who to ask. The access part is administration and takes an afternoon; these four are the work and they take weeks.
Why stage it?: Because each group produces people who can help the next, problems surface while they are cheap, and the support load stays survivable. Rolling out to everyone at once puts every question in the same week at whoever set it up, which slows the whole thing down while looking faster on the plan.
What gets missed most often?: Saying clearly what material is permitted. People who are unsure quietly do not use the tool rather than asking, because asking feels like inviting a refusal. That single unanswered question suppresses more use than any gap in training, and it costs nothing to answer.