A VP I work with has gotten genuinely good at this. Not good in the way people mean when they say “she’s picked up some AI tools.” Good in the way you get good at something you’ve actually lived inside. She catches the model’s drift mid-sentence, she knows which of its instincts to trust and which to override, she’s built something with it that took months, not a weekend.
Nobody on her team knows that.
Not because she’s hiding it. Because there’s no good moment to bring it up. You don’t open a Monday standup with “I’ve gotten fluent in something none of you can see yet.” So she sits on it. She watches her team work the way they’ve always worked, a step behind a gap she can’t casually mention, and she goes quiet about the thing she’s most excited about.
I asked her why she hadn’t said anything.
“Because the second I show them, it stops being my thing I figured out and starts being the thing the manager knows that we don’t.”
That sentence explains more about how AI fluency actually moves through organizations than most of what gets written about the skills gap. The assumption is that the problem is access – to tools, to training, to budget. But the leaders furthest ahead aren’t being blocked by any of that. They’re going quiet on purpose, for reasons that make complete sense to them.
Fluency doesn’t transfer the way a framework does. You can’t hand someone six months of iteration in a meeting. They’d have to be with it the way you did. Nobody has that time, least of all the people reporting to you. So leaders learn to undersell it. To mention the tools casually, almost apologetically. It looks like patience. It’s usually fear.
I’ve watched it land badly when a leader doesn’t undersell it. They get excited, demo something, and the energy in the room goes quiet and defensive. Not because the team doesn’t want to learn. Because what they heard was: the gap between us just got named out loud. Leaders remember that moment. They don’t repeat it.What gets missed is that the silence doesn’t close the gap. The team feels it anyway, as distance, without context for what they’re looking at or how long it’s been growing.
I asked her what she thought would actually happen if she just said it plainly. Not a big reveal. Not a demo. Something closer to: six months ago I was getting the same results you’re getting now. Here’s the thing I kept doing wrong. Here’s the week it started clicking. Here’s where I still get it wrong.
She thought about it. “I think they’d feel behind for a week. And then I think they’d feel ahead of where they are now.”
That’s the whole trade. A week of discomfort for a head start they don’t currently have. The version of going first that works isn’t the polished demo. It’s the unpolished account. The confused version, not just the fluent one. You’re not closing the gap for them. You’re showing them it’s a path because they can see your footprints in it.
Most leaders choose the familiar discomfort of staying quiet over the one they’d have to walk into on purpose. The team stays where they are, feeling the distance without knowing what it is.
She hasn’t done it yet. That’s not a criticism. It’s the honest end of the story. The insight about what it would cost her team came easily. The decision to act on it is harder, because it means giving something up: the private satisfaction of having figured something out on your own, the version of competence that doesn’t need to explain itself.
Nobody else can see what you see right now. That’s not a flex. It’s a responsibility with a shelf life.
The loneliest part of the orchestrator’s job isn’t figuring out the tool. It’s deciding, every day, whether to say so.
