“Leaders are using AI constantly but they’re not saying it out loud — they’re afraid of what the team will think.” — mastermind discussion, Dec 2025
Session context: 2025-12-05_Mastermind — surfaced during discussion of AI adoption friction inside organizations, when a member shared that a client’s leadership team was actively concealing AI use from their direct reports.
Core Idea
A specific and recurring pattern in executive coaching: leaders who are personally using AI extensively — for drafting, thinking through strategy, preparing for conversations, synthesizing data — are concealing this from their teams. The concealment is not malicious; it is anxiety-driven. Leaders fear being seen as inauthentic (“my ideas aren’t really mine”), incompetent (“I need AI to think”), or hypocritical (“I’m restructuring roles and I’m using the technology that might replace them”).
The trap is that the concealment backfires in exactly the way the leader fears. Teams are not oblivious. They notice that the leader’s communication quality has changed, that preparation quality has shifted, that responses to complex questions come faster and with more structure. When the team can observe the outputs but not the process, they fill the gap with their own interpretation — often more destabilizing than the truth. “Did someone else write this?” “Is there a consultant they’re not telling us about?” “Are these even their real views?”
The leadership coaching work here is not convincing leaders to be transparent about AI use because transparency is virtuous. It’s helping them see that the concealment is already not working — the signal is leaking without the framing. Voluntary transparency with framing is more authoritative than discovered transparency without framing.
There is also a second-order team effect: when a leader conceals AI use, it implicitly signals to the team that AI is something to be ashamed of or hidden. This makes bottom-up adoption harder. The fastest way to normalize AI use in a team is for the leader to name their own use openly, including where it helped them and where it didn’t.
Practical Application
The Transparency Reframe — use with leadership clients who are concealing AI use:
- Ask: “What specifically are you afraid the team will think if they know you’re using AI?” Get the exact fear — don’t let them generalize.
- Separate the legitimate concerns (authenticity, intellectual ownership) from the anxiety-driven ones (appearing less capable). Work with the legitimate concerns.
- Ask: “If your team knew you were using AI and framed it well, what would you want them to take from that?” (Leaders almost always have a constructive answer here.)
- Help the leader design a 60-second “use case disclosure” — specific about what they use AI for, what it helps, and where the human judgment still sits. This becomes the framing when they choose to name it.
- Optional: share with the team as a deliberate team-culture signal, not just a personal disclosure.
Related Insights
- Insight - AI Adoption Requires Both Top-Down Vision and Bottom-Up Permission — the transparency trap undermines both dimensions: the top-down vision is communicated incoherently, and the bottom-up permission signal is suppressed
- Insight - Mandated AI Fails, Participatory AI Spreads — The Adoption Mechanism That Actually Works — leaders who hide their own use while mandating team adoption send contradictory signals; participatory adoption requires the leader to model curiosity openly
- Insight - The AI Paralysis Triad — Fear, Doubt, and Overwhelm as Compounding Blockers — leaders in the transparency trap are experiencing their own version of the triad; they need the same triage as any client
- Insight - Safe Container as Transformation Prerequisite — The Mechanism Behind Coaching Results — this work requires a safe container; a leader won’t name a fear about appearing incompetent in a coaching relationship that doesn’t feel safe
Evolution Across Sessions
This establishes the baseline for the AI transparency dynamic inside organizations. Future sessions should track whether this pattern shows up differently by organizational culture, industry, or leadership archetype — and whether any members have found specific disclosure language that lands well with teams.