Why Admitting ‘I Don’t Know’ Made Me a Better Leader

Spoiler: It involved a lot of nodding, coffee, and Googling under the table.

Act I: The Curse of the Expert

When I was younger, back when my hairline was still optimistic and I was still one of the youngest people on the team, I thought leadership meant knowing everything.

If someone asked me a question in a meeting and I didn’t have an answer, I felt a pang of panic, like I was a magician who’d just run out of rabbits. I’d bluff, stall, overcompensate, and speak like I was an auctioneer on speed.

This belief, that leaders must have all the answers, is seductive. It’s baked into how we promote people. The one who always seems to “know stuff” gets a tap on the shoulder. We reward certainty. We praise confidence. We love a good “visionary.”

And for a while, I wore that mask well. I read voraciously. I memorized frameworks. Knew all the current buzzwords. Polished my PowerPoint animation skills to wow the crowd. But deep down, I was terrified that one day, someone would ask me a question I couldn’t fake an answer to, and the whole illusion would unravel like a Gantt chart the moment someone says ‘just a small scope change.’.

But as luck would have it, eventually, it happened.

Act II: The Great Unraveling

I’d been promoted to lead a team responsible for a complex, multi-million-dollar initiative. Everyone was there. Engineering, sales, marketing, and one terrifying VP who was always perpetually pissed off and spoke in bullet points.

Someone asked a question and it was a good, and totally valid, one. The kind that starts with something like, “How will this scale globally if our current architecture is bound to a regional schema?” (Translation: “Are we totally screwed in six months?”)

It was like someone threw a switch that turned off my brain. I froze. Does not compute...blink blink...come on brain "activate!". But my brain was DOA,

I knew some things. Enough to fake it. But not that particular answer. And my normal "tricks", redirecting, restating the question to buy time, or throwing out a confident “Great question, we’re already on top of it”, felt…just...wrong. Disrespectful even. Because I genuinely didn’t_ _know the answer to the question and any response that I gave would be deceitful.

So, for the first time in my young career, I did something radical. I did something that my wife to this day would say that I never do. I said, “I don’t know. But I’ll find out.”

Time stood still. I waited for someone to revoke my badge and bring me an empty file box. Or even worse, throw me into the sea of irrelevant middle managers. Or the worst thing of all, that I had disappointed my team. But instead everyone nodded. What the what just happened?!?!?

And then someone else, someone brilliant, spoke up and said, “Actually, I’ve been looking into this. Here’s what I think…”

It was like opening a dam. One by one, the others in the meeting weighed in, including me. Ideas flowed. The room lit up with collaboration. It was fantastic. Like being part of the collective. (a Borg for my Trekkie friends.)

In that moment I realized something profound. My job wasn’t to know everything. My job was to create space for the right people to bring the answers forward.

Cue record scratch. Cue my transformation. Cue "I Can See Clearly Now" on Spotify. (OK, so Spotify didn't exist back then, but you get the gist.)

Act III: The Humble Rise

Leadership is not about having all the answers. It’s about creating the conditions where answers can emerge.

That means hiring brilliant people and letting them shine. It means knowing enough to ask the right questions, but not being afraid to say, “I don’t know” when you hit the edge of your knowledge. And it means getting comfortable, deeply comfortable, with uncertainty. Just the other day one of the data scientists on my team was talking about a model she was recommending we apply. Both myself and my manager looked at each other and said "yep, you've exceeded our knowledge. We trust you." We didn't need to know all of the intricacies of the model. We just needed to ask the right questions to be comfortable that it was the correct path forward, and then get the hell out of the way.

Now, I know what you’re thinking. “That’s adorable. But isn’t this just glorified hand-waving?”

Not at all. Leading without having all the answers doesn’t mean you’re useless. It means you:

1. Hold the vision. You set the destination, even if you don’t have the map. Your role is to define the “why” and “what,” then let your team help you figure out the “how.” (and know when to stay out of the way.)
2. Build the team. Surround yourself with people who are smarter than you in key areas. (And for the love of efficiency, stop pretending you’re the only one who understands microservices, user research, or what in the hell Kubernetes actually is.)
3. Facilitate dialogue. Create a culture where people feel safe saying “I’m not sure,” or “Have we considered…?” or even “This is completely asinine and here’s why.”
4. Model curiosity. Ask great questions and invite dissent. Be more interested in the truth than in being right.
5. Decide bravely. When the data’s murky and no one has a perfect answer, YOU must make the call. That’s not guesswork. That’s judgment. And, ding ding ding, it’s YOUR job.

Act IV: Confessions from the Middle Seat

Let’s be honest. Leading without all the answers is not glamorous.

It’s messy and it’s being vulnerable. It requires unlearning (read deprogramming) years of corporate conditioning that says “looking smart” is more important than “being real.”

I’ve had moments where I was the least informed person in the room. Moments when I had to tell my team, “I need your help.” Moments when I had to say, “I got that wrong.” Showing that kind of humility let's people know that it is OK to not have all the answers and reinforces that you are a team and not a one person show.

But I’ve also had moments when someone on my team pulled me aside and said:

“Thank you for creating a space where I could speak up.”

“You always make it safe to say what we’re really thinking.”

“I trust you, even when we don’t know the answer yet.”

Those moments? They’re everything, because people don’t want perfect leaders. They want human leaders. Leaders who are humble, who listen, who admit mistakes, and who are relentless about learning. I reiterate, THEY WANT HUMAN LEADERS.

Act V: What I Learned (the Hard Way)

So, here’s what I’ve learned on the rocky road of not-knowing and eating more than my share of humble pie:

1. Confidence and certainty are not the same thing. You can be confident in your team, your values, and your direction, even if you’re uncertain about the next step.
2. Saying “I don’t know” earns trust. It shows integrity. It invites collaboration. And it teaches your team that they’re allowed to not have all the answers too.
3. People want to be empowered. When you stop hogging the “answer spotlight,” others will step into it. And often, they’ll come up with solutions better than anything you could have invented. Stepping back also fosters personal growth as well as reinforces the value of team input.
4. Good leaders solve problems. Great leaders teach others to solve them. And that means being a guide, not a guru. (I also considered the "give a man a fish..." analogy, but that's so overused.)
5. The best answers often emerge in dialogue. Which means your job is to start the conversation, not end it with a mic drop. Practice active listening instead of contemplating your counter move. It's not a game of chess. Be present in the moment and listen.

Act VI: Tips for the Recovering Know-It-All

If you’re reading this and thinking, “Yeah, but what if people think I’m incompetent? Well you'd not be alone in that thinking. That fear runs deep.

Here are some practical ways to build the muscle of leading a team without having all the answers:

1. Replace certainty with curiosity. Instead of “Here’s what we’ll do,” try “What’s the most important thing we need to understand?”
2. Use scaffolding language. Phrases like “From what I understand so far…,” or “This is one way we could approach it, but what am I missing?” build credibility without pretending omniscience.
3. Practice visible learning. Say things like, “When I first heard this, I thought X. But after hearing your input, I realize Y.” Let your team see your thinking evolve. One of my favorite sayings (I have a lot of them if you're a regular reader of this blog) is accredited to Albert Einstein. To paraphrase: "The ability to change one's mind in light of new information is a sign of intelligence." The premise is that it reflects intellectual humility, adaptability, and a willingness to learn and grow. Which contrasts with stubbornly clinging to outdated beliefs, even when presented with evidence to the contrary. (I'm sure we all know a few of these people.)
4. Create decision rituals. Use frameworks (e.g., RACI, DACI, decision memos) to shift focus from “Who knows?” to “How do we decide?” You'll find that using this kind of structure come crunch-time is a real game-changer. So plan in advance and have this information at the ready.
5. Celebrate learning moments. Did someone catch a flaw in your plan? Celebrate it. That’s culture-shaping and a good opportunity for you to grow as well.

Act VII: The Funny Thing About Wisdom

Here’s the punchline.

The longer I lead, the more I realize how little I actually know.

Every new initiative, every team, every market shift reminds me that today’s best practices are tomorrow’s cautionary tales. The world’s moving fast. Technology is changing faster, especially this new world of AI. And no one, not me, not you, not that VP who I'm sure still speaks in bullet points, has all the answers.

But that’s okay. Because leadership isn’t about answers. It’s about courage. The courage to admit what you don’t know. The courage to listen when others disagree. The courage to move forward even when the path isn’t clear. The courage to believe that you will figure it out together.

Epilogue: The Badge of Honor

So if you’re a new leader, or an experienced one that is still haunted by the myth of the all-knowing boss, here’s your permission slip:

You don’t have to know it all. You just have to show up. With clarity. With curiosity. With humility. And yes, with enough caffeine to survive that 4 p.m. “10 minute quick sync” that will somehow take 75 minutes. (You know who you are, but I honestly love our late day chats.)

If you can do that. If you can lead without pretending, you’ll build something far more powerful than answers.

You’ll build trust.

And trust, my friends, scales better than any architecture I’ve ever seen. (Yes, even better than Kubernetes!)

Wishing you all the best

Mike