Every team has one. The person who folds their arms when AI comes up, calls it a fad, and carries on exactly as before. Maybe a few of them. And here is the thing owners get wrong: they treat it as an attitude problem to be overruled, when it is almost always a fear that has never been said out loud.

Get the doubters on board and a rollout spreads by itself, because the person who fought it hardest becomes your best advert once they have felt it save them a Friday afternoon. Try to force it and you get logins nobody opens and a quiet resentment that poisons the whole thing. This guide is about the difference between the two.

Why people actually resist

The word “sceptic” makes it sound like a debate about the technology. It rarely is. Underneath, resistance is usually one of a few very human worries.

  • They think it will make them look daft. Trying a new tool in front of colleagues, getting it wrong, not knowing the right words. Nobody wants that, so they avoid it and call it scepticism.
  • They are quietly worried about their job. If a machine can do part of what I do, where does that leave me. This one is rarely said aloud, and it is the one that hardens people the most.
  • They have been burned before. Every few years something gets sold as the future, everyone gets forced onto it, and it turns out to be more hassle than it was worth. They are not being cynical. They are pattern-matching from experience.
  • They genuinely do not see what is in it for them. Nobody has shown them a single thing it would do for their actual day. Why would they bother.

Notice that not one of these is fixed by telling someone to try harder. They are fixed by dealing with the real worry, and mostly by proof.

Why a mandate backfires

The tempting move is to make it official. Everyone will use the new tool, starting Monday. It feels decisive, but it can create resistance before the tool has proved useful on the team’s real work.

A mandate turns a tool into a chore. People do the minimum to be seen complying and get no value from it, which confirms every doubt they already had. Worse, forcing it on the job-fear crowd makes the fear worse, not better, because now the thing they were nervous about is compulsory. You end up with a company full of licences and no adopters, and a harder job winning them back than if you had never pushed.

You cannot order someone to be enthusiastic about a tool. You can only show them it is worth their while and let them arrive there themselves.

What to try instead: one measured task

The whole game is proof, on their own work, aimed at the thing they hate.

Sit with a sceptical colleague and choose one low-risk job they know well: a weekly report, repeat customer replies or notes after a meeting. Do the task together, then compare the full time, including checking and correction, with the original process.

The point is evidence on their own work, not enthusiasm about AI. They can see what the tool did, what still needed judgement and whether the test was worth repeating.

A few things make this land:

  • Pick their worst task, not your favourite feature. The pain has to be theirs, or it is just a demo.
  • Let them drive. They should be the one typing by the end, so it feels like something they can do, not something done to them.
  • Be honest about the limits. Show them it drafts and they check, so it is clearly a helper and not a replacement for their judgement. That honesty is what kills the job fear, because they can see they are still the one in charge.

Build the habit, do not just light the spark

One good session creates a spark. A habit is what keeps it lit. People slide back to the old way the moment it gets busy, so make the new way the easy one.

Let measured examples do the talking. Share the baseline, the result, the review time and the limits, then let colleagues decide whether the same test applies to their work. Check in later, keep approved prompts for common jobs and make it easy to report where the tool failed.

Do not expect everyone to adopt at the same pace. Give people a safe test, a route to decline and a clear owner for questions. Adoption is a result to observe, not a behaviour to promise.

Where to take this

Winning the doubters is the human half of a calm rollout. The rest, sharing tools, sharing context, ground rules, data safety and cost, is in our pillar guide, Rolling AI out to your team without chaos. Read that for the full picture, and grab the one-page AI policy so the keen ones stay sensible. When the full team roll-out course lands on our courses shelf, getting people to use it is a lesson in its own right.

If you would rather work on this alongside people who do rollouts for a living, that is exactly what The £1,000,000 AI Blueprint in Leigh is for. Half a day at Bedford High School in Leigh, laptops open, with time to work on a plan for your own team. See the event page for current booking details.

And to turn this into a simple plan for your own team, grab our free resource pack from the free resources shelf.