I was in a board-level strategy session about three months into a new CTO role. The CFO asked me a direct question about infrastructure costs for a product line I was still getting my head around.
Every instinct said: bluff. Say something plausible. Sound confident.
Instead, I said: "I don't know. I'll have the numbers to you by Tuesday."
The CFO nodded. The meeting moved on. Afterward, the CEO pulled me aside: "Good answer."
I felt exposed. He was telling me I had done something right.
What I got right wasn't the admission. It was stopping the performance and starting to be useful.
Leaders Are Trained to Perform Certainty
Watch how most leaders respond when they don't know something. They speak in confident-sounding generalities. They redirect to adjacent topics they do understand. They say "good question" and then answer a different question entirely.
This isn't dishonesty. It's survival behavior from years of being evaluated on having answers.
The problem is your team sees through it. The people closest to the work see your knowledge gaps before you finish your sentence. What they're watching for isn't whether you know the answer. They're watching to see if you're honest about when you don't.
Bluffing doesn't fool anyone. It teaches your team to bluff too.
Garry Ridge Called It "Dumbassery"
Garry Ridge spent 25 years as CEO of WD-40. By the time he stepped down, the company had grown from $300 million to $3.5 billion in revenue. More than 90% of employees were actively engaged. And 98% said they loved telling people where they worked.
His philosophy wasn't about being the smartest person in the room. He gave himself the title Dean of Dumbassery. His point: awareness of what you don't know, plus the willingness to work on it, beats arrogance every time.
WD-40 replaced the word "failure" with "learning moments." Not as a motivational poster slogan. As a real operating principle. Mistakes weren't career-ending events. They were data. The culture rewarded people for naming what they got wrong and explaining what they'd do differently.
A culture like this doesn't come from a performance playbook. It comes from a leader who goes first. Who sits in a room full of executives and says: "I don't know. What do you think?"
What Bad Bosses Do
Research from Step It Up HR found 99.5% of people surveyed had experienced at least one type of bad boss. One of the most common patterns? The boss who was never wrong.
Not the boss who got things wrong. The boss who got things wrong and couldn't admit it. Who reinterpreted facts to fit conclusions already reached. Whose certainty was always highest precisely when the ground beneath it was shakiest.
People don't leave companies. They leave managers who make them feel stupid for knowing more than the person in charge. When you pretend to know something you don't, you signal two things: your ego matters more than accuracy, and admitting uncertainty is not safe here. Your team absorbs both lessons immediately.
The Army Taught Me the Other Side of This
In the military, "I don't know, but I'll find out" is a complete, correct answer to almost anything. There's no shame in it. You say it, you find out, you report back.
The Army also taught me what happens when people fake it.
When someone doesn't know a procedure but won't admit it, people get hurt. Equipment breaks. Missions fail. There's no softer way to say it. Pretending to know something in a high-stakes environment isn't bravado. It's negligence.
Corporate life rarely carries those stakes. But the dynamic is identical. When your team sees you bluff through ignorance, they learn bluffing is acceptable. Problems go unreported. Decisions get made on bad information. The costs compound quietly until they don't.
Your Team Already Knows What You Don't Know
Most leaders miss something. Your team has usually already mapped your knowledge gaps. They've watched you long enough to know where your blind spots are. The question isn't whether they know. The question is whether they feel safe enough to fill the gap.
When you model intellectual humility, when you say "I'm not the expert on this, let's hear from Sarah," you do several things at once.
You tell your team their knowledge has value. You create safety for others to admit uncertainty. You get better information faster. And you build trust, the type which survives a crisis.
Henley Business School's research on senior leaders backs this up. Admitting uncertainty creates space for colleagues to develop and lead. It removes rigid thinking patterns. It opens the door to fresh perspectives on strategy and decisions.
The admission isn't weakness. It's an invitation.
The Practical Switch
Saying "I don't know" isn't enough on its own. What matters is what comes next.
There are three ways to handle not knowing:
1. Admit it and commit to finding out "I don't know. I'll research it and get back to you by [specific time]."
2. Admit it and bring in someone who does know "I'm not the right person for this. Let's get Lee on the call... this is his area."
3. Admit it and make it collaborative "I don't have a view on this. What do you see?"
All three are better than a bluff. All three build credibility faster than certainty theater.
The one thing to avoid: admitting you don't know without any follow-through. "I don't know" as a full stop signals indifference. What you're going for is intellectual honesty plus action.
When You Own Your Gaps, Your Team Fills Them
The unexpected benefit of dropping the performance? Your team starts showing up differently.
When the leader stops pretending to have all the answers, the people who do have answers finally speak. I've watched quieter engineers become the most valuable voices in a room once the senior leader stopped filling every silence with confident-sounding noise.
You don't have to have all the answers. You have to be the person willing to ask the right questions and act on what you hear.
Garry Ridge built a $3.5 billion business on this principle. He didn't do it by being the smartest person in the room. He did it by being the most honest one about what he didn't know, and by creating a culture where everyone around him felt safe enough to do the same.
There's a word for leaders who pretend to know everything: isolated. Cut off from real information, real problems, and the real capability of their teams.
There's a better word for the ones who don't: trusted.
So here's what's worth sitting with today. What is your team not telling you because they assume you already know?
Find out. Say "I don't know" and mean it. Then watch what opens up.