Why people resist AI at work, and how to bring them with you

When a company introduces an AI tool and nobody uses it, the usual explanation is that the tool wasn’t good enough. More often, the people it was meant for weren’t brought along.

AI adoption is a change in how people work, and people have reasons to be wary. Understanding those reasons is the quickest route to getting past them.

Why people hold back

• They think it will replace them. The fear is rarely said out loud, but it shapes how people treat a new tool.
• It looks complicated. If nobody has shown them how it helps with their own work, it is easier to ignore.
• They worry about their data. What is the tool storing, who can see it, and is it being used to judge them?
• The old way works. Familiar processes are comfortable, even when they are slow.

Usage is still catching up. Pew Research Center found in September 2025 that 21% of US workers said at least some of their work was done with AI, up from 16% a year earlier. Most people are still on the sidelines, which means most teams have room to do this well.

Six ways to bring people with you

1. Say plainly what the tool is for

Don’t leave people to guess. Explain which tasks it will take on, which stay with people, and how the two fit together. In healthcare, for example, AI can help clinicians go through scans and records faster, while the diagnosis and the conversation with the patient stay with the doctor. Specific examples like that do more than general reassurance.

2. Involve people before the rollout

Nobody likes change handed down to them. Ask the team which parts of their week are most tedious, let them try tools on their own tasks, and take their feedback seriously. A tool chosen with the team gets used. A tool chosen for the team is often ignored.

3. Deal openly with data and ethics

People will use a tool more freely when they know what happens to what they type into it. Publish a short, plain policy: which tools are approved, what data may go in, who can see outputs, and who to ask when something is unclear. Companies that explain how their systems work, and where people can challenge a result, avoid a lot of quiet resistance.

4. Keep teaching

Skills build confidence. Offer short, practical sessions on real tasks in your own business, not a general lecture on AI. Large providers such as Amazon publish free training that can supplement your own. Aim for role-based learning: what a finance analyst needs differs from what a sales lead needs.

5. Show real results

People trust what they can see. When AI cuts the time to produce a weekly report from four hours to one, say so, and say how. Let the person who benefited tell the story rather than management.

6. Start small and celebrate it

You don’t need to change the whole company at once. Choose one area, such as customer enquiries or data entry, measure the work before and after, and share the results. Early wins make the next step easier to ask for.

What happens if you skip the people part

The tool gets installed, a few enthusiasts use it, and the rest of the team carries on as before. After six months the licences are up for renewal and nobody can show what changed. That is a common reason AI projects get cut.

If you’re planning a rollout, it’s worth asking how ready your people are as well as your data and systems. The AI Readiness Index covers skills, attitudes, ownership and capacity for change alongside the technical questions, and our work on AI implementation and automation includes training and a usage policy, not only the build.