You bought the AI subscription, announced it at the Monday meeting, and a month later three people use it. The rest nod politely and carry on as before.
That's the normal result, not a failure. Here's what works better.
Why people hold back
It's rarely stubbornness. People hold back because they're afraid it makes their job smaller, because the last tool they were told to adopt was a headache, or because they don't know what to ask it. Some simply have no spare time to learn something new.
Treat those as real reasons. A mandate doesn't answer any of them.
Start with one person and one task
I've done this rollout inside a company, and I started small. I piloted the tool with one colleague, picked one real task, and got that one thing working properly.
A single working example is worth more than any presentation. Once someone can say "this saved me an hour on that job," the rest of the team listens differently.
Show the result, not the policy
Skip the company-wide announcement. Show people the specific thing, on their own work, in a few minutes. Nobody adopts a tool because of a memo, but plenty of people adopt one after watching a colleague finish a dull job in a fraction of the time.
Watch who actually uses it
Most AI tools show you who's using them. I rolled one out to about fifteen people and checked the usage numbers regularly to see who took to it and who dropped off. That told me where to spend my time, instead of guessing.
A low number isn't a verdict on the person. It usually means they got stuck once and never came back.
Coach the hesitant ones, a little at a time
The people who dropped off needed help, not pressure. I coached them in frequent, hands-on sessions, nearly every day at first: look at one real task, try it together, and leave them with something that worked.
Frequent beats one big training day. A half-day workshop is forgotten by Thursday, but time spent on your own work sticks.
What not to do
- Don't mandate it on day one. Forced adoption produces logins, not use.
- Don't hold one big training day. It covers everything and teaches nothing.
- Don't promise it will save time before it has. Show it first.
Where I fit
Getting a team to use AI is part of what I do alongside advising on it and building it. It's one of the things I handle as an IT consultant and AI solutions architect, and it pairs with the tooling side in AI document intake and where AI helps and where a script wins.
If your team has the tool but not the habit, get in touch for a free consultation and tell me where it's stuck.