Why Employees Resist AI at Work
I recently came across an article suggesting that companies and organizations need to be legally prepared for employees who resist AI for religious reasons. This isn't a piece about religion, so I'm setting that particular angle aside. But the article got me thinking about something I find much more interesting: the human behavior underneath AI resistance.
Because even when religion isn't part of the equation, plenty of people feel reluctant, resistant, or unsure about AI. And if we want to understand why, we have to look past the technology itself and at what it stirs up in people.
The Three Camps
AI is everywhere now, woven into how we operate both personally and professionally. People ask it about medical concerns, share deeply personal information with it, and lean on it for everything from planning their vacation to their kid's birthday party. Organizations are adopting it just as quickly. My husband is an attorney, and his firm recently began using AI in a limited capacity, with training on the legal ramifications of misusing it and a clear understanding that human judgment still has to remain part of the process.
When it comes to how people respond, I tend to see three camps.
There are the enthusiasts, who are genuinely excited. For them, AI meets a need for variety and possibility. It can be a doctor, a sounding board, a second brain, a planner. The range of what it can do feels endless, and that's thrilling to them.
There are the willing, who are open to giving it a try without much fuss.
And then there are the resisters, who dig their heels in and say AI simply isn't for them. It's a robot, and they're not willing to hand it that much power or control.
On a personal level, people are free to land wherever they land. But things get much more complicated when the choice is taken away, when your employer tells you that using AI is no longer optional.
What Resistance Is Really About
Here's what I've come to believe: for people who resist AI at work, the reluctance usually isn't really about the technology. It's about comfort, control, and safety.
When someone is told they have to use AI, a cascade of questions can follow. How secure is my job now? Is this tool going to replace me? If I use it well, am I proving that I'm no longer necessary? And if I lose this job, then what? Those aren't irrational fears. They're the natural response of someone whose sense of stability has just been disrupted without their input.
There's also a disconnection that happens in how AI often gets introduced. People are rarely asked whether they're open to it. Instead, the message tends to be: here's the new program, it's AI-based, this is what you'll be doing, and your options are to adapt or to leave. That approach can leave people feeling like they don't matter, like their experience and judgment weren't part of the decision at all.
When circumstances feel destabilizing, people tend to reach for one of two things: certainty, meaning safety, comfort, and control, or significance, meaning the sense that they're important, valued, and worthy. The forced introduction of AI can threaten both at once. It undermines someone's sense of control over their own role, and it can quietly communicate that they're replaceable.
That may be the furthest thing from what the organization intends. But intention and interpretation are two very different things.
The Gap Between Intention and Interpretation
Organizations generally adopt AI for reasons that feel entirely positive from where they sit. They see increased productivity, smoother workflows, reduced stress, and less mental and emotional load on their teams. From the leadership vantage point, they're offering a benefit.
But that's not always how it lands in the moment.
When someone who has been doing their job effectively for years is told that AI will now handle half of their role, the intended message might be "we're making your work easier." The message actually received can be "you're replaceable, and what you've been contributing isn't as valuable as you thought." When that happens, people can start to wonder whether the real bottom line is money rather than people.
This is the heart of so many workplace breakdowns: one group sees a decision from one perspective, the other group experiences it from a completely different one, and there's often no conversation that bridges the two. Leadership sees efficiency and benefit. Employees see uncertainty and threat. And without a chance to talk through not just the what but the why, that gap only widens.
Why AI Feels Different From Past Technology
It's worth acknowledging that many of the people resisting AI have adapted to enormous technological change over their careers. People who have been in their roles for ten, fifteen, or twenty years have navigated new devices, new software, and new systems again and again. So why does this feel different?
I think it comes down to structure. When a new software program or device arrives, it usually comes with a manual. There's a defined way to use it, a clear set of steps to follow. It's contained.
AI isn't like that. There's no straightforward manual that tells you to enter this prompt, then this one, then this one. Instead, you have to essentially teach the platform how you think, how you communicate, and what you need from it. That takes a lot of upfront trial and error, a lot of specific prompting, and a lot of figuring it out on your own. For someone who values structure and predictability, that open-endedness can feel deeply uncomfortable. It doesn't feel safe. It feels out of their control. And learning something new that offers so little scaffolding is genuinely hard.
Finding the Middle Ground
None of this means organizations shouldn't adopt AI. It means the way they introduce it matters enormously.
There's a middle ground available. It might sound like: we're going to use AI for these specific things, and here's how we'll help you get comfortable with it. It might include reassurance that feels real, not just stated: we value you as an employee, this is meant to make your work easier, and your job isn't in jeopardy because of it.
When people understand not just what is changing but why, and when they feel supported through the discomfort of learning rather than left to sink or swim, the resistance tends to soften. Not because the technology changed, but because the environment around its introduction accounted for how people actually experience change.
That's the piece that so often gets missed. The resistance was never really the problem to solve. It was a signal about what people needed and weren't getting.
If you're feeling this resistance yourself, or noticing it in your organization, I'd love to hear from you. Find me on LinkedIn or Substack at Kim Keane Consulting.