You made the call. AI isn’t optional anymore, for your company, for the people who report to you. You’ve commissioned the training programs, designated the change champions, stood up the cohorts. From where you sit, implementation is underway.
What you can’t see from altitude is what it costs the people you’ve trusted to carry it.
Not the skeptics. Not the resisters. The ones who said yes, running the sessions and translating the tools for colleagues who’ve never touched a prompt in their professional lives.
They’re quietly drowning. Not because they’re incompetent. Because you’ve handed them a teaching role in a subject they’re still learning themselves. And because you never named that this is an unusual and costly ask. And because you haven’t named it, they can’t either.
Here’s a portrait that’s more common than you know.
He’s a senior manager at a company you’d recognize, going through a significant AI push. Smart, high-agency, committed to the mandate. He’s been named a change champion and is leading colleagues through training on tools and workflows he’s still learning himself. He has his own team to run, new responsibilities that landed recently, and an organizational change in his department he didn’t see coming.
He hasn’t slept well in days. When he finally says out loud what he’s been carrying, it sounds like this: I feel like I’m doing so many things and I don’t know if I’m actually doing anything well.
Ask him what he’s teaching his cohort, and he’ll tell you, accurately, that he knows slightly more than they do. That he surprises himself sometimes with how much he’s learned. That there are moments when he can diagnose a problem quickly and it feels good. But that he also knows, unmistakably, that he isn’t an expert, and that he’s supposed to be leading people through a transformation he’s in the middle of himself.
This is the experience you aren’t seeing, not in your dashboards, not in your all-hands updates, not in whatever version of the story reaches you, filtered by however many layers stand between you and him.
He isn’t going to tell you. Because he was picked for this because he’s capable and enthusiastic and doesn’t complain. Because he doesn’t want to look like he can’t handle it. Because you never built him a place to say: this is harder than I expected, and here’s what would actually help.
He’s, by every measure you track, a successful change champion. And he’s quietly experiencing a form of imposter syndrome that isn’t irrational. It’s an accurate read of unfamiliar territory. He’s one step ahead of the people he’s teaching, and that’s enough to be useful. It isn’t enough to feel legitimate.
You probably believe the hard part of AI change management is the resisters.
That model is incomplete in a way that’s costing you. The people most at risk in an AI transformation aren’t the resisters. They’re the early adopters you’ve handed institutional authority with no institutional support, your change champions, your most capable, committed people, the ones you’re counting on to pull the rest of the organization forward.
When those people quietly burn out, none of the costs show up in your metrics, and you pay for all of them.
A change champion running on empty, teaching from the edge of his own knowledge while managing a room full of anxious colleagues, isn’t transmitting the same thing as one who feels resourced and legitimate. The curriculum stays the same. The delivery doesn’t. The difference shows up in the moment that matters most, when someone in the cohort hits a wall and needs a person who’s been there, not a slide deck.
You also lose a bridge you didn’t know you had. Your change champion isn’t just a trainer. He’s the person who understands both the mandate and the ground-level reality of implementing it, the one who can tell you what’s actually happening in the organization, if you’ve built the kind of relationship where he feels safe saying it. Burn him out or let him spiral without noticing, and you lose that intelligence. You lose it quietly, too, because he won’t tell you he’s losing it.
He’s also watching how you treat him. So is everyone else. Whether you see your most committed people when they’re stretched, whether you name it, whether you do anything about it, teaches your whole organization what leading this transformation actually looks like at your company. That lesson gets learned whether you mean to teach it or not.
None of this calls for a new program or a bigger budget. It calls for attention, which at your level is the scarcest thing you have.
I didn’t do this well myself. When we rebranded Tender Greens, the project touched everything: new signage on every restaurant, new menu boards, product packaging, uniforms, the website, the whole digital presence, and it meant explaining the decision to a thousand employees so they could explain it to our guests. The truth is my co-founders and I didn’t fully believe in the rebrand ourselves. We handed the rollout to a team who did their best to execute what we’d asked of them, without ever feeling it in their own hearts. I never named that gap for them. I let them carry something I hadn’t settled for myself and called it execution.
That’s the ask you’re making of your change champion too, whether you’ve named it or not.
Start by naming the ask explicitly. When you designate someone as a change champion, say out loud what you’re actually asking him to do: lead people through something you yourself are still learning, on top of everything else already on his plate. Not as a warning, as an acknowledgment. I know this is an unusual ask. I know you’re not an expert. I’m choosing you because you have the judgment and the relational intelligence to be credible even without the expertise, and I want you to know I see the difference between what I’m asking and what I’m officially calling it. That sentence costs you nothing and changes everything about how he shows up for it.
He also needs somewhere to give you the real report, because right now he’s giving you a sanitized one. Not because he’s dishonest, but because you haven’t built the relationship where the honest version feels safe to deliver. Create a regular, private touchpoint, not a status meeting, not a dashboard check-in, where the only question is what’s actually hard about this and what he needs that he doesn’t have. Then listen without solving. What you hear there is worth more than anything your implementation tracking can tell you.
And it’s worth recognizing what he’s actually doing as a specific leadership skill. Walking into a room of anxious colleagues and saying, honestly, I’m learning this alongside you, and here’s what I’ve figured out so far, and having that land as credible instead of undermining, is hard. The authority it takes doesn’t come from mastery. It comes from trust, presence, and the willingness to be seen not knowing. That’s worth naming, worth rewarding, worth protecting. The champions who can do it are worth more to your implementation than any curriculum you’ve bought.
You’re probably measuring adoption rates, completion percentages, productivity gains. Those are the right things to measure. They aren’t sufficient.
The question you’re probably not asking is how the people carrying this mandate are actually doing. Not in the aggregate. Individually. The specific person you designated to lead the training in operations, the one in finance, the one in product. What’s it costing them? What do they need that they haven’t asked for? What aren’t they telling you because you haven’t built the relationship where it’s safe to say it?
AI transformation isn’t a training program. It’s a leadership challenge running through every layer of your organization, including, and especially, the layer just below yours. The people translating your mandate into reality are doing the hardest kind of teaching: leading from the middle of the learning curve, in public, on behalf of an organization watching to see if this is real.
They deserve to be seen, not managed, not measured. Miss that, and the transformation you think is underway is thinner than your metrics say it is.






