There was a period — maybe six months into building PipelineRoad — when a major shift in one of our key channels made our primary growth strategy suddenly less effective. The approach that had been working wasn’t working anymore, and I didn’t have a replacement plan. Bruno and I were staring at the numbers, and for the first time, I didn’t have a confident answer for what to do next.
My instinct was to fake it. To walk into the next team meeting with manufactured certainty, lay out a plan that sounded good, and project the kind of decisive leadership that startup mythology tells us founders are supposed to embody. I almost did it.
Instead, I said something closer to the truth: “The landscape has changed. I don’t have the full answer yet, but here’s what I’m thinking, here’s what I’m testing, and here’s how we’re going to figure this out together.”
That moment taught me something I’ve relied on ever since: honesty about uncertainty, paired with visible effort to resolve it, builds more trust than false confidence ever will.
The Certainty Trap
There’s an expectation — sometimes explicit, usually implicit — that leaders should have answers. The team looks to you for direction. Clients look to you for expertise. The mythology of entrepreneurship is full of visionaries who always knew the way. Steve Jobs had conviction. Bezos had the long view. The narrative is always about certainty.
But the lived experience of leading a company is mostly uncertainty. You’re making decisions with incomplete information. You’re navigating situations you’ve never been in before. You’re dealing with market shifts, team dynamics, and competitive pressures that don’t come with instruction manuals. If you’re honest about it, you don’t have the answer more often than you do.
The trap is pretending otherwise. When a leader consistently projects certainty they don’t feel, two things happen. First, the team stops questioning decisions, because the leader seems so sure. This eliminates the kind of constructive challenge that catches bad calls before they become expensive mistakes. Second, when the leader is eventually proven wrong — which is inevitable — the credibility damage is amplified. They weren’t just wrong; they were wrong while being emphatic about being right.
What “I Don’t Know” Actually Communicates
Most leaders avoid saying “I don’t know” because they think it communicates weakness. In reality, it communicates several things that are far more valuable than false certainty.
It communicates self-awareness. A leader who can accurately assess the boundaries of their knowledge is a leader the team can trust to not lead them off a cliff through overconfidence.
It communicates respect. Telling your team “I don’t know yet” is implicitly saying “I’m not going to waste your time and effort on a plan I’m not confident in.” That’s more respectful than handing them a directive you know is half-baked.
It communicates an invitation. When a leader admits uncertainty, it opens the door for the team to contribute. The smartest person in the room might not be the one with the title. By acknowledging that you don’t have the answer, you create space for someone else to offer it.
The Crucial Second Half
Here’s where the nuance matters: saying “I don’t know” is only effective when it’s followed by visible action. The full sentence isn’t “I don’t know” — it’s “I don’t know yet, and here’s what I’m doing to figure it out.”
During that uncertain period at PipelineRoad, I was transparent about not having a plan, but I was also transparent about the process of finding one. I shared the data I was analyzing. I talked through the options I was considering. I reported back on the experiments I was running. The team could see me working the problem in real time.
This combination — honesty about the gap plus visible effort to close it — produced something unexpected. The team became more engaged, not less. People offered ideas they might have kept to themselves if I’d walked in with a false master plan. The solution we eventually found was better than anything I would have come up with alone, precisely because the uncertainty invited collaboration.
The Frequency Matters
There’s a calibration here that’s worth being honest about. A leader who says “I don’t know” occasionally builds trust. A leader who says “I don’t know” about everything erodes confidence. The skill is in knowing which uncertainties to share and which to process privately.
My general rule: share uncertainty about strategic direction. Process uncertainty about your own competence privately. The team needs to know when the map is being redrawn. They don’t need to know when you’re having a crisis of confidence at three in the morning. Those are different kinds of not knowing, and they require different kinds of handling.
The Paradox of Confidence
There’s a paradox in all of this that I find genuinely interesting: the leaders who are most comfortable admitting what they don’t know tend to be the ones the team has the most confidence in. Not because uncertainty is inherently inspiring, but because the willingness to be honest about it signals a kind of intellectual courage that’s rarer and more valuable than performed decisiveness.
I trust people who can say “I was wrong” or “I’m still figuring this out” more than I trust people who have a ready answer for everything. The ready-answer people are either genuinely brilliant — which is rare — or they’re performing confidence to manage their own anxiety. The ones who admit uncertainty and then work the problem visibly are the ones I want to follow.
The best leaders I’ve encountered don’t lead with answers. They lead with process, with honesty, and with the quiet conviction that the team can figure it out together — even when no single person has the solution yet. That’s not weakness. That’s the realest form of strength I know.