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. It almost never works.

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 works instead: one saved hour

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

Sit with a doubter for twenty minutes. Not a training session, just the two of you and the one job they groan about most: the weekly report nobody reads, the same five customer replies typed from scratch, the notes written up after every meeting. Do that one task with AI, together, and let them watch an hour of tedium turn into ten minutes.

That single moment does more than any presentation. It moves the conversation from “this is a threat I do not understand” to “hang on, that would give me my Friday back”. You are not asking them to believe in AI. You are showing them it just did their least favourite job for them.

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 the early wins do the talking. When your first small group starts finishing at four instead of six, everyone hears about it, and that word of mouth from a colleague is worth more than anything from the boss. Check in a week later and help with whatever tripped them up. Keep a couple of ready-made prompts for the common jobs so nobody faces a blank box. And notice out loud when someone uses it well, because a little recognition turns a one-off into a routine.

Do not expect everyone at once. You will get a keen few first, then the middle follows when they see it is normal, and the last holdout comes round when standing still starts to feel odd. That is fine. A rollout that spreads because people want in beats one that stalls because they were pushed.

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 our AI Automation Masterclass in Manchester is for. Half a day at Heron House, laptops open, and you leave with a plan for your own team. Tickets are normally £20. This one’s free, a limited-time offer to launch the series.

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