“You’re not enough.”
I hear it after keynotes, in DMs, on calls with founders who’ve raised real money and still hesitate before hitting “post.”
Because that whisper isn’t only living in the heads of the women you might be trying to hire or keep. It’s sitting three seats down from you right now, in your architecture reviews, your retros, your promotion cycle. Whether you notice it is a leadership skill. Not a personality trait.
The Numbers Describe People Already on Your Team
This isn’t abstract. Girls Who Code and Accenture found that women leave tech roles at a 45% higher rate than men, and a non-inclusive culture (not skill, not ambition) is the single biggest reason. The World Economic Forum calls the pattern the “drop to the top”: women hold 24.4% of managerial roles in STEM, but only 12.2% reach the C-suite, a steeper drop than in any other sector they measured.
Read that as a leader, not as a statistic. If you run a mixed tech team, some share of the people on it are already deciding, quietly, that this isn’t worth staying for. The exit interview will say “better opportunity.” It won’t say “I never quite believed I belonged in this room, and nobody gave me a reason to think otherwise.”
It’s Not a Confidence Problem. It’s a Questions Problem.
On the podcast episode #186, with AJ Lauer, we got into why so many capable people, especially women, hesitate to pitch, apply, or speak up, even when they clearly know the material. AJ’s read on it stuck with me: it’s rarely about intelligence or access to information. It’s about not knowing what questions to ask and being afraid that asking will expose that you don’t already know.
There’s older research that backs this up in a way I didn’t expect. You’ve probably heard the “confidence gap” statistic about women only applying for jobs when they meet 100% of the listed qualifications, while men apply at 60%. Harvard Business Review’s Tara Sophia Mohr actually went and asked people why, instead of assuming. “I didn’t think I could do the job well” turned out to be the least common answer, for both men and women. The real reasons were about reading application instructions literally, not wanting to look presumptuous, and not knowing which of the listed requirements were actually negotiable.
That’s not a confidence gap. That’s a systems literacy gap, dressed up as a personality trait. And it means the fix isn’t “believe in yourself more.” It’s a leader making the unwritten rules explicit before someone has to guess them alone.
The Habit That’s Quietly Making This Worse
I wrote about this pattern in Your Team Is Managing You (And You Don’t Even Know It): leaders who project constant competence, who always arrive with the answer, teach their teams that questions are inconvenient and uncertainty is weakness. So people stop asking. And they stop telling you what they actually don’t know.
For someone already carrying the “not enough” whisper, that leadership habit isn’t neutral. It confirms the story. If the leader never says “I don’t know, let’s figure it out,” why would the engineer who’s two years into the role risk saying it first?
Three Things to Actually Do This Week
1. Ask the obvious question out loud, on purpose. In your next architecture review or planning session, say the thing a junior person might be too afraid to ask. You model that questions are signal, not weakness.
2. Make the unwritten rules explicit. Before your next promotion cycle, write down what “ready” actually means, and share it with the whole team, not just the people who ask. If someone is 70% of the way there and hesitating, tell them directly. Don’t wait for them to self-select out the way the HBR research describes. Mastering Tough Conversations has a structure for exactly this kind of 1:1.
3. Tailor how you invite input. A Base Thinker needs logical permission to ask (“we haven’t covered edge cases yet, so raise them”). A Base Harmonizer needs relational safety first, before the technical ask. One script doesn’t work for a whole team. That’s the whole premise behind Communication Intelligence (CQ): reading what a specific person needs before you decide how to lead them.
Your Version of This Week’s Challenge
The Pulse asked women to catch the whisper once this week. As a leader, yours is a little different: catch the silence once. The next time someone doesn’t ask a question in your meeting, don’t assume it’s because they already know the answer. Ask them, later, one on one, what they were thinking and didn’t say. You might be surprised how often “nothing” was actually “something I didn’t want to say out loud.”
If you’re a leader with women on your team (or you are one yourself), the free STEMinist Summit on October 15 and 16 is built for exactly this conversation, with speakers from Intel, NVIDIA, and NASA and no “just believe in yourself” panels. And if you want the fuller conversation behind this article, go listen to Episode 186 with AJ Lauer.
