The short answer.
Roll out pieces of work, not licenses. Go team by team: each team gets one named piece of its own work that ChatGPT, Claude, Copilot or Gemini prepares, with written instructions, one owner and one person who checks the result. People keep using the assistant because it does their own work, the way their best colleague does it, and the next team starts when the first piece of work is in daily use.
Seats and a training session are not a rollout.
Giving everyone a seat and a training session produces a few enthusiasts and a lot of unused seats. The training shows the assistant in general; on Monday each person faces their own work with no instructions for it, and goes back to the old way.
A rollout that sticks starts from a piece of work the team repeats every week: the month-end close checklist, the brief before a client call, the reply to a new inquiry. Written down and tested, that piece of work is a workflow, and the workflow is the unit you roll out.
Before anyone gets a seat.
Before anyone gets a seat, settle three things.
- Approve one assistant.Choose the one your company already pays for. One approved assistant means one set of instructions and one account to administer.
- Write two paragraphs of rules.The first says which assistant is approved and on which account. The second says what information may go into it and who to ask when someone is unsure. Is it safe to put company data into ChatGPT, Claude, Copilot or Gemini? sets out the questions to answer.
- Name the owner of the rollout.One person, by name, usually the head of operations, the chief of staff or the owner. The rollout owner chooses the order of teams, holds the weekly check and decides when the next team starts.
The first team and its first piece of work.
The first team is the one with a piece of work that repeats every week, starts from records someone can export or copy, and already has one person who reviews it. Choose that piece of work before anyone in the team opens the assistant.
Then develop the workflow. Capture how the team’s best person does the work, write it as instructions the assistant follows, test it on last month’s cases, and hand it to the team with a note on when to run it and who checks. From working workflow to daily use: the rollout checklist covers that first month step by step.
A person decides at every step. The workflow prepares the draft, the checklist or the packet; the checker reviews it, and anything that sends, pays or changes a record waits for that person’s approval.
How the second and third teams follow.
The second team starts when the first team’s workflow is in daily use, not before. The rollout owner then repeats the same steps with the next team: one piece of work, written instructions, an owner, a checker and a test on real cases.
The second and third teams move faster than the first. The rules are written, the rollout owner has done the steps once, and other teams have watched colleagues use the assistant on real work, so they ask for their own workflow. Choose the next team where a piece of work is ready, or where work passes between teams and gets stuck. A team already running proposes its second piece of work once its first is in daily use.
What the leader does each week.
The leader of an AI rollout spends one short meeting a week with the owner of each workflow in progress, and asks three things.
- Did the team run the workflow this week?If not, what stopped them: a missing input or a step that does not fit.
- What did the checker correct?The owner decides whether each correction changes the instructions.
- What is ready to start next?The next team, or the next piece of work in a team that is already running.
The leader also runs a workflow every week. That does more for the rollout than any announcement.
How you know the assistant is being used.
You know an AI rollout is working when each named workflow runs on schedule, run by the team that owns the work, without anyone asking. Seat counts and logins show only that the assistant is installed. Installed, used or useful? gives three questions that tell installed, used and useful apart. For each workflow, write down beforehand what “in daily use” means, and check against that line every week.
How long a rollout takes.
A rollout takes as long as the sequence takes in your company: the rules and the owner first, then one team’s first workflow into daily use, then the next team. Two things set the pace.
- The owner’s attention.Each workflow in progress needs its owner to test it, answer questions and decide on changes. Run one workflow per team, and two or three across the company at once. Attention runs out before anything else.
- How ready the records are.A workflow that starts from a clean export or a standard form moves quickly. A workflow that starts from records scattered across inboxes waits until someone decides what the input is.
The first 90 days of an AI adoption plan lays the same sequence out across a first quarter.
A rollout sheet for one team.
Copy these headings into a document, one sheet per team. Fill the sheet in with the team’s lead before anyone runs the workflow.
- The team.Its name and its lead.
- The work.The one piece of work the assistant prepares, in one sentence.
- What it starts from.The records, files or form the workflow reads, and where they come from.
- What it produces.The draft, checklist, summary or packet, and who receives it.
- Who runs it.The role that runs the workflow, and when.
- Who checks.The person who reviews each result and approves anything that leaves the team.
- The owner.One name: the person who keeps the instructions current and decides on changes.
- What “in daily use” means.How often it runs, by whom, and what the checker signs off.
- What comes next.The team’s second piece of work, once this one is in daily use.
Illustrative example.
Take a 70-person engineering consultancy that already pays for one assistant. The head of operations owns the rollout and writes the two paragraphs of rules. Finance goes first, because its month-end close checklist repeats every month, starts from an export of the accounting system, and is already reviewed by the controller. The finance manager owns the workflow; the controller checks every result. Once the checklist is in daily use, project delivery follows with a weekly status summary, checked by each project’s director, and then business development with a first draft of each proposal’s scope, checked by the partner who signs it. Each Monday the head of operations asks the workflow owners the three questions.
What is different in a company of under 200 people.
Most rollout advice is written for large enterprises, with a steering committee, a training program and a platform team. A company of under 200 people rolls out differently.
- The rollout owner is an operator.The head of operations or the owner runs it. IT sets up accounts and access.
- The rules are short.Two paragraphs, written by the rollout owner, are enough to start.
- Every team is in reach.The leader knows each team’s lead, so the order of teams is settled in one conversation.
That is where 10X the ROI of your existing AI comes from in a small company: the same seats, pointed at named work, one team at a time.
Where to start.
A rollout is the third step of a plan. How organizations plan their use of AI covers the whole method: plan it, develop the workflows, deploy them. FullyPowered Planner is where the plan lives: you set out your teams, their roles and the work between them, and choose what each team builds first. The Workflows Directory holds free workflow templates to start from. To develop a team’s first workflow with us, see the 3-Day Workflow Sprint and the 2-Week Workflow Sprint.