Vic Sol · Decision DeskEditable template · 15 min to use
If you impose AI, your team slows it down: the 4-week plan
For anyone who must "roll out AI" to a team that did not ask for it and would rather they take part than obey.
When to use it
You were assigned to "bring AI" to your area and the start date is already set.
You announced a tool, the room went quiet and nobody opened it afterwards.
A previous attempt stalled on its own, without anyone saying no.
The sheet
When you say "we are going to use AI", many do not hear "productivity"; they hear "cuts". If you do not talk about that, fear fills the silence. This plan starts there.
Week
Objective
Activity
Signal of progress
The mistake that makes the team slow it down
1 · The why
The team knows which problem you want to solve and where the freed time goes.
30-minute meeting. You name the problem with a number (illustrative: "quotes take three days"). You say honestly where the freed time goes.
Someone asks a hard question out loud.
Showing the tool before explaining the why.
2 · They choose
The team picks the first task to improve.
Each person writes down what eats their time. They vote for one task. You do not vote.
The chosen task is not the one you would have chosen.
Choosing the task for them "to move faster".
3 · The trial
Try the AI on that task, with a before number.
Two or three people use it on real work and note where it helped and where it failed.
There is a documented mistake and nobody hid it.
Measuring people instead of the task.
4 · The review
Decide together: keep, adjust or stop, and pick the next task.
30-minute meeting. Before and after number. You honor what you said in week 1 about the freed time.
The team proposes the second task without being asked.
Declaring success without a number, or changing where the freed time goes.
Problem we are going to solve: ____________ · The freed time will be used for: ____________ · Task chosen by the team: ____________
How to fill it in 15 minutes
Fill in the line "the freed time will be used for" first. If you cannot write it honestly, do not start yet.
Write the problem with a number, even an approximate one marked as such. "Improve productivity" is not a problem; it is a phrase.
Leave the week 2 task blank. The team fills it in; that is what makes them actually use the tool.
Plan week 3 with two or three people. A small trial with a visible mistake teaches more than a general launch.
The most common mistake: skipping week 1 because "everyone already knows why". They do not. If they only receive the order, they look for ways not to use it.
The line that is almost always missing
The week 1 promise about the freed time, honored in week 4. The team agrees to try because you told them where that time would go. If in week 4 it goes elsewhere, the next plan never starts, however good it is. If the team helps decide, they use it; if they only receive the order, they slow it down.
Vic Sol · Decision Desk · vicsol.org/resources/ · Free to use with attribution. This sheet structures a conversation; it is not legal, financial or audit advice.
Open the .docx in Word (or the .xlsx in Excel) or print it before the meeting.
Fill the fields with the team; leave the blanks visible, they are the discussion.
Close with one owner, one date and one next action. Nothing else.
Prompt
Generate this sheet for your case
Paste this prompt into ChatGPT, Claude or Gemini together with your proposal, process or policy. It reproduces the sheet with your data and flags what is missing.
Act as an operations director with 15 years in change management, who has watched AI rollouts stall because they were imposed and designs plans where the team chooses the first task.
Context I am giving you:
- My team, its size and what it does: [ ]
- What I was asked to do (and by whom): [e.g. "roll out AI in the area this quarter"]
- The business problem I really want to solve, with a number if I have one: [ ]
- What the freed time will honestly be used for: [ ]
- What the team has already heard or suspects: [ ]
- Approved tools: [ ]
What I need: produce the four-week plan with exactly this structure:
1. Week 1, the why: objective, activity, signal of progress and the mistake that makes the team slow it down. Include the two-minute script where I explain the problem before showing the tool and say where the freed time goes.
2. Week 2, they choose: how the team picks the first task to improve, without my vote.
3. Week 3, the trial: who tries it, with which before number, and how the mistake gets documented without pointing at anyone.
4. Week 4, the review: how we decide together to keep, adjust or stop, and how I honor what I said in week 1.
Output format: a four-row table (Week · Objective · Activity · Signal of progress · Mistake that slows it down) followed by the week 1 script. Maximum 450 words. No introduction.
Rules:
- If I did not tell you what the freed time will be used for, do not invent it: write [DATA PENDING] and tell me the plan should not start without that line.
- Do not choose the week 2 task for the team; leave that field blank with instructions.
- No language about cuts or people's efficiency; tasks are measured, not people.
- Mark every assumption as an assumption.
- If critical information is missing, ask me at most 3 questions before answering.
- Answer in plain, direct business English, with no sales adjectives.
What to check in the answer:
Does the week 1 script say which problem and where the freed time goes, or does it only describe the tool?
Did week 2 leave the choice to the team, or did the AI "suggest" it for you?
Is each week's signal of progress observable, or is it a wish?
Vic Sol