TL;DR: Your team's resistance to AI isn't about the technology—it's about past experience. They've watched rollouts happen to them before, not with them. The way forward isn't more training or bigger announcements. It's listening first, proving it works second, and letting early wins do the talking.
I had a call last week with a manufacturer in Madison. Good company, solid team, real business. The owner told me, "My people just aren't comfortable with AI. They're resistant. We need better training."
I asked him one question: "When was the last time you brought in new software and it went well?"
Long pause.
He listed four different systems from the past ten years. CRM that nobody used. Inventory platform that didn't work the way they expected. Accounting software that ate an extra two hours every month. And new email rules that broke their workflow.
"So," I said, "your team isn't afraid of AI. They're afraid of being set up to fail again."
He stopped talking. Then he said, "Oh."
That "oh" is the moment everything changes.
The Resistance Is Rational
Here's what I've learned leading AI adoption across dozens of companies: people who look "resistant" to new tools aren't luddites. They're experienced. They've seen what happens when leadership gets excited about the next shiny thing without thinking through what it actually means on the ground.
Your team has been through this. They remember the last time someone came in saying, "This will save you so much time." Then it didn't. Or it did, but only after months of fumbling, after their daily work got slower while they learned the system, after they realized the tool was built for a completely different workflow than the one they actually use.
So when you talk about bringing in AI, they're not thinking about the glossy demo in the board meeting. They're thinking about all that.
That's not resistance. That's wisdom.
The Three Real Fears
Under almost every objection I hear, there are three fears that actually matter.
First: I'm going to be replaced.
I've sat in rooms where a CEO joked about how AI will "cut staffing costs" or do the work of three people. Then they wonder why their team seems nervous.
Your people heard that. They're processing it. And it's hard to be enthusiastic about something that might eliminate your job.
The joke might land funny in a leadership meeting, but it echoes differently when you're worried about your mortgage.
Second: I'm going to look incompetent.
"What's a prompt?" someone asks in a training session. Two hundred people hear them ask. Now they're the person who doesn't get it.
Or worse—your team is sitting in a training about something they don't use yet, with language they don't understand, feeling behind. That feeling sticks.
Most people aren't afraid of AI itself. They're afraid of being the person who doesn't know how to use it. They're afraid of looking slow or outdated in front of their peers.
Third: This is going to create more work, not less.
They've seen "time-saving tools" that saved time for exactly nobody. Tools that required documentation. Tools that needed workarounds. Tools that added a step to their process.
The software stack gets more complex. The training gets longer. The system you're bringing in doesn't actually talk to the system you already have.
Your team is thinking: "They're going to promise this saves time. Then I'll spend six months learning it, and I'll be doing the same job in a more complicated way."
That's not cynicism. That's pattern recognition.
Why Training Doesn't Fix This
When companies hit resistance, the standard move is to invest in training. More workshops. Better materials. Lunch-and-learns about generative AI. Lunch-and-learns about prompt engineering.
I get the logic. If people just understood AI better, they'd be less afraid.
But that's not where the problem is.
The problem isn't knowledge. It's trust.
Your team doesn't need to understand how transformer models work. They need to trust that you're not going to roll this out and abandon them. They need to believe that this is being done with them, not to them. They need to see that you're thinking about their day-to-day work and not just the efficiency spreadsheet.
A two-hour webinar doesn't rebuild trust. A big announcement doesn't rebuild trust. A mandate doesn't rebuild trust.
Trust comes from experience. It comes from seeing that this actually works. It comes from watching someone they respect use it successfully, without it falling apart.
That's not something you can teach. It's something you have to prove.
Show, Don't Sell
The companies I've worked with that handled AI adoption well didn't do it with big announcements. They did it with small experiments.
Instead of rolling out AI across the entire company at once, they found one team dealing with one real problem. They listened to what was eating up their time. They found a tool that could actually address it. Then they supported that team while they figured it out.
And then—this part matters—they let that team tell their story.
An email from a manager about how great AI is? People glaze over. A conversation between coworkers where one says, "Hey, I used this tool yesterday and it cut my analysis time in half"? People listen to that.
Your early adopters become your advocates. Not because you told them to be, but because they've seen the thing work with their own eyes and hands.
The 30-Day Framework
Here's what I've found works. It's simple, but it requires patience.
Week 1: Listen
Talk to your team. Ask what frustrates them about their current work. Ask what takes longer than it should. Ask what they wish they had more time for. Don't mention AI yet. Don't pitch anything. Just ask and listen. Write it down.
You're going to be surprised. The things that bug them most are rarely the things you expected.
Week 2: Match
Look at what you heard in Week 1. Now ask: where could AI actually address this?
Maybe it's document summarization. Maybe it's handling first-draft writing so someone doesn't start from scratch. Maybe it's analyzing data to help someone make a decision faster. Match the pain to an actual tool. Be honest—not everything AI can do is useful for your business. That's fine.
Week 3: Pilot
Pick one small team and one specific task. Give them a tool. Give them permission to experiment. And—this is important—support them. Not with a training manual. With you or someone they trust available when they get stuck.
Let them try it. Let them fail a little bit. Let them figure out what works and what doesn't for their actual work.
Week 4: Share
Ask that team to share what they learned. Not in a polished presentation. In a conversation. "Here's what we tried. Here's what worked. Here's what was harder than we thought."
That's the story that shifts other people from skeptical to curious.
Then repeat. One team at a time. One pain point at a time. Let the evidence stack up.
The Real Foundation
I've watched this play out at a professional services firm where I led AI adoption with 50+ people. We didn't start with company-wide rollouts. We started with one team, one tool, one problem.
Six months in, people were asking us to bring AI tools to their team. The enthusiasm didn't come from a mandate. It came from seeing something that actually worked.
The companies that struggle with AI adoption aren't struggling because their people are afraid of technology. They're struggling because they didn't invest in their people first. They bought the tool and expected the people to fit around it.
The companies that succeed do it the other way around. They ask what their people need. They find tools to match. They support the people who use them. They let early success create belief.
Technology only works when people do. The best tool in the world fails if your team doesn't trust it or know how to use it. The simplest tool succeeds if your team believes in it and you've set them up to use it well.
That's not sentiment. That's just how people work.
Frequently Asked Questions
Real adoption? Months, not weeks. Show-and-tell adoption, where it's part of people's actual work? At least 90 days, usually longer. You're not just rolling out software. You're building a new habit and proving that it's worth the time to learn. That takes time.
Good. Kill it. Pivot to something else. Your team just learned that you're not going to force them to use something broken. That actually builds trust.
Yes. Because if you pitch AI before you understand the problem, you're selling a solution looking for a problem. Your team will feel it.
There will always be some. But I'd guess it's fewer than you think. And a lot of the people who seem most resistant are actually the ones who've been burned most by bad rollouts before. They might be your most valuable early adopters if they see it work.
Ready to Lead Your Team to AI Success?
Let's talk about how to build adoption the right way—with your people, not at them.
Start a Conversation