There's a moment I remember clearly from early in my leadership career.
I was in a quarterly business review. My CTO looked across the table and asked a direct question about infrastructure costs for the following fiscal year. I had a rough number in my head. I was not confident in it. I had two choices: manufacture some confidence and give the ballpark, or say the truth.
I said, "I don't know. I'll have the right number to you by Thursday."
The room didn't collapse. Nobody walked out. She nodded. The meeting moved on. By Thursday, I sent her a number I trusted.
That moment changed how I lead.
The Lie We're Trained to Believe
From the first day of school, "I don't know" is a failure state. You raise your hand when you have the answer, not when you don't. Every test, every quiz, every performance review drills the same reflex: find the answer, or at least look like you're about to.
By the time you're leading people, this reflex runs deep. Your team looks to you for direction. Your peers expect you to own your area. Your boss wants to hear confidence, not uncertainty.
So you guess. You extrapolate. You reframe the question so you answer a slightly different one. You hold your ground.
The people around you know. They always know. And every time you fake it, you widen the gap between what's real and what you think is real.
What Faking It Costs You
There's a research concept called the Iceberg of Ignorance. Management consultant Sidney Yoshida identified it in a 1989 study of a Japanese manufacturer. His finding: frontline workers were aware of roughly 100% of the problems in their area. Direct managers knew about 74%. Middle management knew about 9%. Senior leadership knew about 4%.
The gap doesn't exist because senior leaders are stupid. It exists because people stop bringing problems to leaders who already seem to have everything under control. When you perform certainty, you train your team to filter what they tell you. Problems disappear from your view, not from reality.
I've watched this play out too many times. A leader projects confidence in a strategy the team knows isn't working. No one says anything, because the leader clearly has it handled. The leader doubles down on a failing approach. Problems compound. By the time the failure becomes undeniable, it's expensive to fix.
Performing competence leads directly to incompetence.
There's also a personal cost. When you commit to a position you're not sure about, you spend energy defending it instead of evaluating it. You start gathering evidence to support your position rather than to test it. You stop seeing clearly.
What Google Found
In the early 2010s, Google ran a research project called Project Aristotle. They studied over 180 of their own teams, trying to work out what separated the high performers from everyone else.
They looked at team composition, seniority, educational background, how often teammates socialized outside work. None of it predicted performance consistently.
What did? Psychological safety. Specifically, whether team members felt free to speak up, admit mistakes, ask questions, and say "I don't know" without embarrassment or punishment.
Teams where people felt safe to be uncertain outperformed teams where they didn't. Not because they were warmer or more collegial. Because they operated in reality instead of in the story their leader was telling.
Information flows freely when people feel safe. It stops flowing when they don't. And a team operating on filtered, performance-safe information will always lose to a team operating on the truth.
What Changed for Me
When I started saying "I don't know" more deliberately, something shifted.
People started bringing me real information. Not the polished version, cleaned up before it reached my level. The raw version: what was genuinely broken, where we had no good answers yet, what the team had been afraid to raise because they assumed I already knew.
I also noticed my team stopped performing too. When your leader doesn't pretend to have all the answers, people stop spending energy on presentation. They put it into the work instead. Meetings got faster. Problems got named sooner. We made fewer expensive wrong turns.
One specific thing I started doing: ending one-on-ones by asking, "What are you uncertain about right now?" Not "What's the problem?" or "What do you need?" but uncertainty specifically. The answers were always worth more than anything I asked in the rest of the meeting.
The shift I wasn't expecting: my own thinking got sharper. When you stop defending positions you're not sure about, you're free to work out whether they're right.
Two Kinds of "I Don't Know"
One kind is abdication. The leader shrugs, offers nothing, and moves on. The team learns their leader is unreliable. Don't do this.
The other kind is an invitation.
"I don't know... and here's what I'm going to do to find out."
"I don't know. Does anyone here have a better view on this than I do?"
"I don't know. Let's work it out together."
The difference is what comes next. Useful uncertainty is paired with action or curiosity. It opens a conversation. It signals to your team their knowledge has value and their input is wanted.
Your team will spot the difference in about three seconds. So be clear on which kind you're modeling.
The Timing
Right now, leaders across every industry are expected to have answers about AI. What will it do to headcount? Which roles are safe? How does the three-year roadmap hold up?
The honest answer for nearly everyone: we don't know.
This week, Meta announced 10,000 layoffs while stating AI will create more jobs in the long run. Perhaps so. Any leader who tells their team they have this period fully mapped out is not telling the truth. And their team knows it.
The leaders who will do well through this period are not the ones with the clearest predictions. They're the ones with teams that feel safe enough to surface real information, adapt quickly, and say out loud when something isn't working. None of that happens if the leader has to perform certainty about a situation nobody understands yet.
It Gets Easier
The first time you say "I don't know" in a meeting with senior leadership, it feels like stepping off a ledge. You half expect confidence to drain from the room.
What happens instead is respect. Not immediately, sometimes. But over time, people learn to trust what you say, because when you don't know you say so instead of bluffing. Your confident statements start to carry real weight, precisely because you're not making them when you're not confident.
Admitting you don't know invites contribution, collaboration, and trust. Not because it's charming or self-deprecating. Because it's true. And truth is what a team needs from its leader above everything else.
What I'd Tell My Younger Self
Stop faking it. Not because it was shameful. Everyone does it. But the gap between what you know and what you pretend to know is exactly where bad decisions live.
Fill it with honesty instead. Your team will trust you more for it. Your thinking will get sharper for it. You'll shed the exhausting weight of keeping all those performances consistent.
You don't need to know everything. You need to be honest about what you do and don't know. It turns out to be one of the most important things a leader does.
So: where right now are you performing certainty you don't have?