If you manage people, you've probably had this exact moment: someone on your team mentions they've been using AI to draft emails or summarize reports, and you realize you have no idea what your policy on that even is. Do you encourage it? Ignore it? Worry about it?
Here's what I hear from leaders again and again: it's not that they're against AI. It's that nobody handed them a playbook for introducing it to a team without causing panic, confusion, or a dozen people quietly using it in a dozen different ways with no guardrails.
The mistake most leaders make
The most common approach I see is silence. Leadership doesn't say anything, hoping the topic sorts itself out. It doesn't. What actually happens is that your most curious employees start experimenting on their own, your most anxious employees start worrying they'll be replaced, and six months later you have a patchwork of ad-hoc habits instead of a team that's actually good at this together.
The second most common mistake is the opposite problem: a top-down mandate. "Everyone will use this new AI tool starting Monday," announced in a company-wide email, with a link to a 40-page technical manual nobody reads. This works about as well as you'd expect.
What actually works
The teams I've seen adopt AI well all did three things differently:
They named it out loud. Not a mandate, just an honest conversation: "AI is already part of how some of you work. Let's talk about it as a team instead of pretending it isn't happening." That single conversation does more to reduce anxiety than any policy document.
They explained the why before the how. People don't resist AI itself nearly as much as they resist feeling replaced or judged. A leader who opens with "this is about giving you more time for the parts of your job that actually need a human" gets a completely different reaction than one who opens with "this will make us more efficient."
They gave people a shared, plain-English starting point. Not everyone needs to become a prompt engineer. They need one consistent, jargon-free foundation so the whole team is speaking the same language, instead of five people each figuring it out separately and unevenly.
You don't need to be the expert
One thing I want to say directly to anyone leading a team who feels like they should already know all this: you don't need to be the most technical person in the room to lead this well. In fact, some of the best AI rollouts I've seen were led by people who were upfront about still learning themselves. That honesty builds more trust than false confidence ever could.
What you do need is a way to bring your team along together, at a pace that respects where they're starting from, without outsourcing the whole thing to a consultant who doesn't know your culture.
A path that doesn't start with a 40-page manual
This is exactly why we built the AI Readiness License for teams and organizations. It gives your whole team the same plain-English training, at the same time, without jargon-heavy workshops or an outside consultant translating tech-speak into human speak for you. Everyone starts from the same clear foundation, and you get to lead the rollout instead of reacting to it.
It's built for exactly the situation most leaders are quietly sitting in right now: people already experimenting on their own, no shared language for it yet, and a nagging sense that "we should probably have a plan for this."
If that's where you are, you don't have to figure it out alone, and you don't have to wait until it feels like an emergency.
Take a look at the AI Readiness License for your team →
As always, if you have questions about what's right for your team's size or stage, just hit reply on any of our emails. I read every one.
— Van Gerald, VG Learning
0 comments