How to Make Your Team Want to Learn AI (Instead of Forcing Them)
I watched a CEO send a memo last year: "Everyone will complete an AI training by end of month. Non-negotiable."
The training was completed. On the surface, all boxes were checked. But I guarantee you - 90% of those people learned nothing they'll actually use, and 100% of them resented being forced.
This is the mistake most leaders make: they think compliance equals adoption. It doesn't. A person can sit through 8 hours of training and walk out with zero commitment to changing anything about how they work.
The skill isn't mandating training. The skill is creating conditions where people want to learn.
WHY FORCING DOESN'T WORK
There's something about being told you "have to" learn something that kills your brain's ability to actually retain it.
When learning feels forced, three things happen immediately:
First, you get resentment. People feel like they're being told their current skills are somehow insufficient. They feel like you don't trust their judgment about what they need to learn. They dig in. Resistance hardens.
Second, you get compliance theater. People show up, check the box, and leave having learned nothing. They're physically present but mentally absent. Your training becomes something they have to get through, not something they're curious about.
Third, you kill intrinsic motivation. The moment you make something mandatory, you shift from "I want to do this" to "I have to do this." And the second form of motivation is always weaker. Always.
The CEOs and leaders I see winning with AI adoption aren't the ones mandating training. They're the ones creating curiosity.
THE CURIOSITY-FIRST APPROACH
Here's what actually works: Lead with a story, not a mandate.
Share a small win. "Sarah in operations just saved four hours a week using this tool. Here's exactly what she did." Not "Everyone should do this." Just "Here's what happened to one of us."
Curiosity is contagious. When someone sees a peer doing something that makes their work easier, they want in. They'll ask, "How'd you do that?" And suddenly, they're learning not because you told them to, but because they want what the other person has.
Make early adopters visible. If three people on your team have started using AI, let them be the teachers. Not you, the boss who mandated it. Their peers. People they trust. People they know won't judge them if they're slow to pick things up.
This is radical. Leaders usually want to be the ones delivering the message. But the research is clear: people learn better from peers than from authority figures. And they definitely learn better from chosen teachers than from mandated trainers.
Start with the frustrated people, not the whole team. Who's been complaining about something being tedious? Who said, "This is so boring, there has to be a better way"? Those people are ready to learn. Start there. Show them how AI solves that specific frustration.
Don't train the whole company. Train the five people who are actively frustrated. Let them solve their problem. Then watch others notice and ask what changed.
THE THREE ELEMENTS OF VOLUNTARY LEARNING
When learning is voluntary, it only works if three things are present. And I mean all three. One missing element and it dies.
First: Perceived relevance. The person has to believe this matters for their actual life, not their theoretical job description. "I need this to be better at what I'm already trying to do" beats "This is the future of work" every single time.
So instead of "Learn AI," say, "We're going to show you how to double your output in your current role using this tool." That's relevant. That's personal.
Second: A safe place to be bad at it. Most people don't want to learn in a group setting where failure is visible. They want a space where they can mess up, ask dumb questions, and not be judged.
Offer optional office hours. One-on-one coffee conversations. A Slack channel where people can ask questions anonymously. A safe failure zone. The moment someone feels publicly embarrassed for not knowing something, their brain shuts down and learning stops.
Third: Visible results, quickly. People need to see that this is working for them. Not eventually, now. Can you show them something they built after 2 hours that feels powerful? Can they see time saved, quality improved, something tangible?
The people who get excited about learning are the ones who see immediate results. So design the learning so the first two hours produce something they actually use.
THE ROLE OF LEADERSHIP IN CURIOSITY-DRIVEN LEARNING
Here's what leaders should do instead of mandating:
Model the learning yourself. Use AI. Publicly. Show your team that you're trying to get better. "I've been using this for a week and here's what surprised me." That's leadership. That's permission.
Celebrate the explorers, not the adopters. Don't wait until someone has perfectly integrated AI into their workflow to celebrate. Celebrate the person who tried it and failed. Celebrate the person asking questions. Celebrate curiosity, not mastery.
Create time for learning that doesn't look like training. "Friday afternoons, from 2-3pm, we're not expected to be in meetings. Use that time to explore something that fascinates you." Done. Suddenly, learning isn't an extra burden. It's part of work.
Ask questions instead of giving answers. "What would you do if you could automate the thing you hate about your job?" Not "Here's what AI can do." Let them discover. Your job is to help them see possibilities, not to convince them they need to change.
THE COMPLIANCE VS. COMMITMENT DIFFERENCE
This is the crux of it:
When you force learning, you get compliance. People do what you asked, but they don't change. Six months later, they're doing the job exactly how they did it before, just with "AI training" added to their CV.
When you create curiosity, you get commitment. People internalize the learning. They build it into their workflow. They teach others. They ask for more advanced training because they're already using the basics.
The first approach makes you feel like you've done your job. The second actually does it.
So if you're a leader thinking about rolling out AI training, stop. Don't mandate it. Instead, ask yourself: Who on my team is already frustrated with something that could be solved faster? Can I show them one tool that solves it? Can I give them space to be curious about it?
Then watch. The curiosity will spread on its own.
Build an AI-Ready Culture. We specialize in helping teams want to learn, not compliance training. Let's design a learning experience that actually sticks.