The data is clear: organizations where leaders explicitly connect AI to career growth are more than twice as likely to see higher adoption. Not twice as likely to see better outputs. Twice as likely to see people actually use it.
And yet most organizations are leaving that entirely on the table.
The conversation happening in most workplaces right now sounds like: “We need you to use this tool.” The conversation that actually moves people sounds like: “Here is how being fluent in this tool makes you more valuable — not less.”
That shift is not a communications update. It is a leadership behavior. And it starts with the manager.
Here are five ways to make it real.
1. Name the fear before it names you.
The number one reason AI adoption stalls at the team level isn’t resistance to technology. It’s unaddressed fear. Fear of being replaced. Fear of looking incompetent. Fear of a future nobody fully understands — including the person running the meeting.
Fear that gets heard loses its power. Fear that gets dismissed goes underground — and becomes the active resistance that quietly derails your rollout.
Before any AI conversation with your team, create the space for honest dialogue. Not a polished town hall. Not a forwarded policy document. A real conversation where the hard parts are allowed in the room.
That’s where trust gets built. And trust is what makes adoption possible.
2. Stop connecting AI to efficiency. Connect it to the person’s future.
This is the single most underused lever in AI transformation.
Research shows that employees are 2.1 times more likely to adopt AI when their manager connects it to their career — not to productivity targets, not to competitive pressures, not to cost reduction.
The message that lands isn’t: “We need to be more efficient.”
The message that lands is: “Here is how fluency in this area makes you more valuable, more versatile, and more indispensable to this organization.”
Every team conversation about AI should have a clear answer to: What does this mean for you — specifically, individually, professionally? If you can’t answer that, your team can’t hear anything else you’re saying.
3. Find your prosumers — and amplify them.
Most organizations try to drive AI adoption top-down: mandates, announcements, training programs. Research from MIT tells a different story. The strongest AI deployments started bottom-up — with the employees who were already experimenting on their own.
Those are your prosumers. They exist on your team right now. They may not be the loudest voices in the room, but they’re the ones quietly getting things done with AI while others are still waiting to be convinced.
Find them. Ask them to share their experience in a team meeting. Let them teach a peer. Give their story a platform.
One real story from someone inside the building is worth more than any external communication campaign. You don’t need a new initiative. You need to stop overlooking the people already leading the way.
4. Model the learning curve publicly.
One of the fastest ways to create psychological safety around AI is for the manager to visibly be learning too.
When leaders only show up with polished AI wins, they accidentally signal that uncertainty is a weakness to hide. That’s the opposite of what adoption requires.
Talk about what you tried. What worked. What didn’t. What you’re still figuring out. When your team sees that you are navigating the same learning curve they’re on — that you’re doing it without shame — they get permission to do the same.
This is not vulnerability for its own sake. It is the specific leadership behavior that lowers the cost of trying, which is the only way to increase the frequency of trying.
5. Make “AI fluency” part of the growth conversation — starting now.
Career development conversations are still happening in most organizations as if AI doesn’t exist. Skills assessments, development plans, promotion criteria — often untouched.
That’s a missed signal to your team. When AI shows up everywhere except the growth conversation, employees draw their own conclusion: this is something being done to me, not for me.
The fix is simple, but it requires intention. Start asking: What AI capabilities would make you stronger in the next role you want? Build that into your one-on-ones. Reference it in development planning. Make fluency something your team is building — not just something they’re being asked to demonstrate.
When AI becomes part of how you talk about their future, it stops being a threat to it.
The Bottom Line
Your team is watching how you talk about AI — and more importantly, how you don’t talk about it. Silence reads as anxiety. Compliance-framing reads as a mandate. Neither produces adoption.
What produces adoption is a manager who can look their team in the eye and make AI feel like something that belongs to their future — not something that threatens it.
That conversation is yours to lead. No one else in the organization is closer to it.