Your People Aren't Rejecting AI—Your Rollout Is
Consider a common scenario: leadership purchases AI licenses, IT announces the rollout, and a training session is scheduled. Three weeks later, usage remains low, and managers question the lack of adoption. This pattern is familiar to L&D teams with every new system, whether a project planning tool, CRM, or LMS. With AI, however, the stakes are higher.
There's something important managers often miss. In many companies having trouble with AI adoption, employees are already using AI. Recent surveys found that 57% to 59% of employees say they hide their AI use from managers. Some stay quiet because they don't know the rules, while others worry they'll seem like they're cheating or not as skilled. This changes how we see the problem. Most of the time, people aren't resisting the technology itself but the way it's introduced. To improve adoption, we need to understand what employees are really pushing back against, and it's rarely the tool.
Resistance Is Rarely About The Technology
People don't dislike AI so much as they dislike change. Behavioral economists call this status quo bias. The classic Samuelson and Zeckhauser experiments showed that people stick with an existing option even when a clearly better one sits right in front of them. [1] Research focused specifically on software adoption finds the same thing.
AI is a big change. It's new, changes fast, and how it works isn't always clear. Even early users can feel unsure. What seems like stubbornness is usually just a wish to stick with what's familiar.
Some teams adapt to change more quickly. Marketing teams often lead adoption because experimenting with new tools is integral to their role, making unfamiliar technology an opportunity rather than a threat. A TMetric analysis found marketers spend nearly twice as much time using AI compared to other teams. If an AI rollout requires an initial champion, marketing is well-positioned to lead.
The Real Objection: "Will This Replace Me?"
When people put off using AI or seem uninterested, it's often because they're simply worried. They need honest answers, not just encouragement. Pew Research found that 52% of U.S. workers worry about how AI will affect their jobs, and only a few think it will create more opportunities than it takes away. [2] A Mercer survey found that 40% of workers fear losing their jobs to AI. [3]
This fear is why some employees hide their AI use. If people think a tool could replace them, they won't be eager to use it openly. They use it quietly to keep up their performance but avoid drawing attention. When adoption efforts ignore these worries, they're basically asking employees to show how replaceable they are, so it's no surprise people hesitate.
The First Blocker: "I Don't Know Where To Start"
People stall because they simply don't know how to use the thing. We often treat AI as if everyone already understands it, but the reality is that the training gap remains significant.
This is a real problem. When experienced employees feel unprepared, they avoid new tools to protect themselves, not because they're lazy. Most people don't want to look incompetent in front of coworkers. Giving clear guidance helps reduce the fear of mistakes, and a lot of resistance goes away. Having identified the challenges, it is important to address them in the correct sequence. Many rollouts approach this in the wrong order.
Start With Managers, Not Licenses
Сompanies buy licenses, send out a company-wide email, and hope people will start using the new tool. This rarely works. Teams watch their managers for signals and respond more to their involvement than to official announcements. When managers set an example and show trust, team engagement goes up. If managers seem unsure, nothing happens. Managers share the same concerns as their teams, along with additional responsibilities. So make managers your "AI champion," support them, and that will lead to effective implementation.
Bring In Someone Who Has Done It Before
This step is frequently overlooked, but it is critical. Expecting already busy managers to become AI implementation experts is unrealistic. A dedicated individual/IT consultancy company should oversee the AI rollout. From designing the process, establishing guidelines, selecting initial use cases, leading early sessions, to training managers to sustain progress.
This individual should serve as a catalyst. Whether assigned from another team or hired specifically, this must be a dedicated role, not an added responsibility for multiple employees. Experienced catalysts accelerate progress, reduce costly errors, and prepare managers to sustain the process independently. The ultimate goal is for the organization to no longer require this dedicated support.
Show People The Destination
Employees are more likely to push through early challenges if they know the purpose. Often, rollouts use vague goals like "we need to be innovative" or tell people to "do more with less."
These don't motivate teams to stick with it when things get tough. Instead, give clear, specific goals:
- What will this team stop doing?
- What does a good week look like six months from now?
- What gets easier, not just faster?
A clear, concrete goal does more to drive adoption than any feature demo.
Concrete Personal Payoff
The unknown is scary. Show real examples to decrease fears of being replaced. Tell your team real stories of people who got better at their jobs, earned more, or moved up thanks to AI. This proves that learning AI makes workers more valuable, not less. Thank early adopters in public. This helps make AI a normal part of work and encourages others to try.
Make The New Way The Easy Way
Not all resistance comes from anxiety. Some employees simply prefer the method that requires less effort, which is a natural tendency. Kahneman described this as the law of least effort: when given two options, people choose the one that is easier. For example, if a new time-tracking tool is more complicated than an existing spreadsheet, employees will continue using the spreadsheet. The same principle applies to AI. If the new process is more complex, employees will default to familiar methods.
Adoption problems aren't just about motivation. A lot of resistance comes from how hard the process is. Making things easier can really boost adoption.
Final Thoughts
To sum up, the pattern is clear. Employees aren't rejecting AI; they're dealing with discomfort, protecting their status, and looking for the easiest way to work, which is normal. Successful organizations get the order right: they prepare managers, bring in an experienced rollout leader, set clear goals and benefits, and make adoption simple. This helps employees who used AI quietly start using it openly, which brings bigger benefits to the whole organization.
Our team used this approach and saw great results. By focusing on managers first, bringing in a dedicated rollout leader, setting clear goals, and making things easier, our team became much more efficient. The real change happened not because everyone got excited about AI but because we tackled the real fears and obstacles.
References:
[1] Status quo bias in decision making
[2] Pew Study Finds 52% Of Workers Fear AI. Smart CEOs See An Opportunity
[3] 40% of Workers Now Fear Losing Their Job to AI — Up From 28% in 2024