Back to Blog

How to Overcome Employee Resistance to AI

Employee resistance to AI is rarely about the tech. It's about fear, trust, and managers who don't know what to say. Here's what actually works.

B

Boon

Author

June 17, 2026

Published

To overcome employee resistance to AI, leaders have to treat it as a trust problem, not a training problem. People resist AI when they fear it will replace them, when they don't understand how it changes their work, or when the rollout happens to them instead of with them. The fix isn't a better tool or a louder mandate. It's managers who can name the fear, explain the why, and give people a real reason to lean in.

Most companies get this backwards. They buy the software, schedule the training, send the all-hands email, and then act surprised when adoption stalls. The resistance was never about the technology. It was about everything the technology made people feel, and the fact that nobody addressed any of it.

Why employees actually resist AI

People don't resist AI because they're stubborn or behind the times. They resist it because they're doing the math on their own job security and not liking the answer.

Research on workplace adoption consistently points to the same root causes: fear of being made obsolete, distrust of decisions they can't see inside of, and a sense that the change is being done to them. That tracks with what Boon sees across its client base. When a rollout fails, it's almost never because the team couldn't learn the tool. It's because nobody gave them a reason to want to.

There's a useful distinction here that most articles miss. Resistance and reluctance are not the same thing.

Reluctance is "I don't know how this works yet." That's a learning curve, and it solves itself with time and support. Resistance is "I don't trust what this means for me." That one doesn't solve itself. It calcifies. If you treat resistance like reluctance, throwing more tutorials at a trust problem, you make it worse. People feel handled, not heard.

The teams that move fast on AI aren't the ones with the smartest people. They're the ones where someone took the fear seriously before asking anyone to change.

The fear is specific, so the answer has to be too

"Will AI take my job?" is the headline fear, but it's rarely the real one once you get into a conversation.

When managers in Boon's coaching work actually sit down with their teams, the fear breaks down into much more specific worries. A senior analyst isn't scared of AI in the abstract. She's scared that the part of her job she's proudest of, the judgment calls she's spent a decade building, is about to be flattened into a prompt. A support rep isn't scared of automation. He's scared his manager will start measuring him against a bot that never takes a break.

Generic reassurance doesn't touch any of that. "AI is here to help you, not replace you" is the corporate equivalent of "we're like a family." Nobody believes it, and saying it out loud erodes the trust you're trying to build.

What works is specific. Tell people exactly what changes and exactly what doesn't. If a tool now drafts the first version of a report, say that, then say what you still expect the person to bring: the judgment, the context, the decision about whether the draft is any good. Name the new skill the job requires now, and commit to helping them build it.

People can handle change they understand. What they can't handle is ambiguity dressed up as optimism.

Managers make or break adoption, and most aren't ready

If you want to know whether an AI rollout will work, don't look at the tool. Look at the managers.

Adoption lives and dies in the conversation between a manager and their team, and most managers walk into that conversation with nothing. They got an email from leadership, a deadline, and zero help figuring out what to say when someone on their team is quietly furious or quietly terrified.

So they do what untrained managers do under pressure. They parrot the company line, they avoid the hard conversation, or they pile on the deadline because that's the part they know how to manage. Boon has written before about the cost of bad managers, and AI rollouts are where that cost shows up fast. A manager who can't lead through ambiguity will turn a manageable change into a morale problem.

This is the part companies underinvest in. They'll spend a fortune on the platform and nothing on the people who have to bring it to life. Boon has made this case in its breakdown of why your managers are the real engine of growth, and AI is the clearest test of it yet.

The skill managers need here isn't technical. It's the ability to hold a hard conversation, sit with someone's discomfort without rushing to fix it, and connect a scary change to something the person actually cares about. That's coachable, which is the whole point of coaching for managers. But it doesn't happen by accident, and it definitely doesn't happen from a slide deck.

What actually works

Across the rollouts Boon has watched succeed, the pattern is consistent. Here's what the teams that get past resistance tend to do.

  1. Start with the fear, not the feature. Before you demo anything, ask people what worries them. Out loud, in a room. The act of naming it takes most of the power out of it.

  2. Find the people who are already curious. Every team has someone leaning in. Give them early access, let them break things, and let them tell their peers what they found. A coworker's honest take beats a leadership memo every time.

  3. Be specific about what the job becomes. Not "your role will evolve." Tell them which tasks go away and which new ones matter now. Vague evolution is what people fear. A concrete new job description is something they can prepare for.

  4. Make it safe to be bad at it. Nobody adopts a tool they're scared of looking stupid using. Build in a stretch of time where fumbling is expected and not graded.

  5. Move in small loops. Roll out a piece, get feedback, adjust, roll out the next piece. Big-bang launches give people one enormous thing to resist. Small loops give them many small things to get used to.

None of these are about the technology. They're about how change feels to the person living it.

Your best people resist hardest

Here's something that surprises leaders. The loudest resistance often comes from your strongest performers, not your weakest.

It makes sense once you see it. Your top people built their status on being excellent at the current way of doing things. They're the expert everyone goes to. AI threatens that the most, because it puts a novice with a good prompt within striking distance of work that used to take years to master.

So your best analyst, your most experienced rep, your go-to engineer, they have the most to lose in status and the most reason to drag their feet. And because they're respected, their resistance spreads. When the office expert is skeptical, everyone else feels justified.

This is also where it connects to burnout. High performers under threat don't just resist, they overwork to prove they're still indispensable, which is its own problem. Boon has written about why high performers burn out, and an AI rollout handled badly is a reliable way to trigger it.

The move isn't to win the argument. It's to give your experts a new place to be excellent. Make them the ones who define how the team uses AI well, who set the standard for judgment on top of the tool. People who feel their expertise is being honored, not erased, become your strongest advocates. The same status that fueled their resistance can fuel adoption, if you point it somewhere.

When resistance is actually a warning

Not all resistance is fear talking. Sometimes the person dragging their feet is the only one paying attention.

If your most careful people are uneasy about an AI tool, that's worth hearing out before you steamroll it. Maybe the tool is making confident mistakes. Maybe it's eroding a quality check that mattered. Maybe it's solving a problem nobody actually had while creating three new ones.

Leaders who treat all pushback as a change-management obstacle will run straight past real risk. The skill is telling the difference between "I'm scared of what this means for me," which is a coaching conversation, and "this tool is genuinely worse," which is a product conversation. You find out by asking and actually listening. A manager who can distinguish fear from judgment is worth more in a rollout than any consultant. That kind of discernment is exactly what good leadership development builds.

The cost of getting this wrong

The companies that lose here won't lose because they picked the wrong AI tool. They'll lose because their best people quietly checked out, their managers fumbled the conversations that mattered, and the fear nobody addressed hardened into a culture that braces for every change instead of meeting it.

AI is not the last big change your people will face. It's the rehearsal for all the ones coming after it. The real work isn't getting one tool adopted. It's building an organization where change doesn't trigger a fear spiral, where managers know how to lead through uncertainty, and where people trust leadership to tell them the truth about what's happening to their work.

Coaching is how that capability gets built. Not a one-time workshop, but ongoing support that helps managers practice the hard conversations and helps leaders model the steadiness their teams take cues from. Across Boon's programs, session attendance runs at 89%, which matters here for one reason: people only keep showing up to something that's actually helping them with a problem they have right now. Leading a nervous team through AI is exactly that kind of problem.

You can buy any tool. You can't buy a workforce that trusts you when things get uncertain. That gets built one honest conversation at a time. Boon Scale puts 1:1 coaching in front of everyone who needs it, and pairs each manager with a coach for the specific conversations a rollout demands, not a deck they forget by Friday. If your rollout is stalling and you suspect the tool was never the problem, come talk to us.

Frequently asked questions

Why do employees resist AI at work?

Employees resist AI mostly out of fear: fear of being replaced, fear of losing the expertise that gives them status, and fear of a change being done to them without input. The technology itself is rarely the issue. Resistance is a trust and communication problem, which is why better training alone almost never fixes it.

How do you overcome employee resistance to AI?

Start by naming the fear out loud before you introduce any tool. Be specific about what changes in each person's job and what stays the same. Recruit the people who are already curious to lead by example, make it safe to be bad at the tool while learning, and roll out in small loops instead of one big launch. Above all, equip your managers to lead the conversation, because adoption lives or dies there.

Why do high performers resist AI more than other employees?

High performers built their status on mastery of the current way of working, so AI threatens them most by putting less experienced people within reach of work that used to take years to master. Their resistance also spreads, because respected people make skepticism feel justified. The fix is giving them a new place to be excellent, like defining how the team uses AI well.

Is employee resistance to AI ever a good thing?

Yes. Sometimes the person resisting is the one paying closest attention, and their pushback is flagging a real flaw, like a tool that makes confident mistakes or removes a quality check that mattered. Leaders should distinguish fear-based resistance, which is a coaching conversation, from a legitimate warning, which is a product conversation.

What role do managers play in AI adoption?

Managers are the single biggest factor in whether an AI rollout succeeds, because adoption happens in the conversation between a manager and their team. A manager who can hold a hard conversation and connect a scary change to what people care about drives adoption. One who avoids the discomfort or just repeats the company line stalls it.

How can coaching help with AI adoption?

Coaching builds the specific skills managers need to lead through change: holding hard conversations, sitting with discomfort, and connecting change to what people value. It also builds the broader muscle to handle uncertainty, so the next big change doesn't trigger the same fear spiral. Boon's management coaching hub covers how that works in practice.

Newsletter

Get more like this

Leadership insights, coaching research, and practical frameworks delivered to your inbox.

Ready to transform your leadership development?

Discover how Boon can help your organization build resilient, effective leaders at every level.