Early in my career, I believed that credibility came from having answers. The faster you could respond to a question, the more confident you sounded, the more competent you appeared. This is the implicit curriculum of most professional environments: certainty is rewarded, hesitation is suspect, and “I don’t know” is something you say only as a last resort, preferably while already pivoting to a guess dressed up as an opinion.
It took me years to understand that this instinct — the compulsion to always have a take — is one of the most destructive habits a person can develop. Not because having answers is bad, but because the habit of manufacturing answers when you don’t actually have them erodes the one thing that matters more than expertise: trustworthiness.
The Cost of Pretending
I’ve sat in enough client meetings, enough strategy sessions, enough pitch rooms to know what happens when someone is bluffing. It’s not always obvious in the moment. People are good at it. They use confident language, they reference frameworks, they anchor to data points that sound relevant. But over time — sometimes over the course of a single engagement — the bluff surfaces. The recommendation doesn’t hold up. The analysis crumbles under a follow-up question. The strategy turns out to be generic advice dressed in the client’s terminology.
The cost isn’t just the bad advice. It’s the trust that evaporates when the gap between what someone claimed to know and what they actually knew becomes visible. That trust is almost impossible to rebuild.
At PipelineRoad, Bruno and I made a deliberate decision early on that we would rather lose a deal than pretend to have expertise we don’t. When a prospective client asks us about a channel or a market we don’t know well, we say so. When we’re uncertain about a recommendation, we frame it as uncertain. When we’re wrong — and we are, regularly — we say that too, as quickly and directly as we can.
This has cost us some engagements. It has also built every lasting client relationship we have.
The Intellectual Honesty Gap
There’s a particular failure mode I see in knowledge work, especially in marketing and strategy: the consultant who has read one book on a topic and now speaks about it with the authority of someone who has spent a career in it. The strategist who has a framework for everything, including things they encountered for the first time last Tuesday. The agency that says “yes, we do that” to every service request because they’re afraid that saying “no” will close the door.
This is not confidence. It’s insecurity wearing confidence’s clothes. And it produces work that is competent at the surface level but hollow underneath — work that sounds right but isn’t grounded in the kind of deep understanding that comes from having actually struggled with a problem rather than having skimmed an article about it.
The gap between genuine expertise and performed expertise is one of the widest in professional life. And the people who can tell the difference — sophisticated buyers, experienced executives, anyone who has been burned by confident incompetence — are the exact people you most want to work with.
What Happens When You Say It
Something interesting happens when you say “I don’t know” in a professional setting. There’s an initial moment of discomfort — for you, sometimes for the other person. It violates the expected social contract. You’re supposed to know. That’s why they’re asking you.
But after that moment, something shifts. The conversation becomes more honest. The other person relaxes. They stop performing too. The discussion moves from a display of credentials to an actual exploration of the problem. And that’s where good work starts.
I’ve noticed this in client strategy sessions especially. The best conversations I’ve had have started with some version of: “I’m not sure about this yet. Here’s what I think based on what I’ve seen, but I want to pressure-test it.” That framing invites collaboration instead of deference. It makes the client a partner in the thinking rather than a passive consumer of my opinions. And it produces better outcomes, because the client usually knows their market and their customers better than I ever will.
Building the Muscle
Saying “I don’t know” is a skill, not just a disposition. It requires practice. It requires a certain comfort with being seen as imperfect in real time. And it requires separating your identity from your knowledge — which is harder than it sounds, especially for people who were praised for being smart growing up.
I practice it in small ways. When someone on the team asks me a question and I’m not sure, I try to catch myself before the reflexive answer lands. When I’m writing, I flag the claims I’m less confident about rather than smoothing them over with authoritative language. When I’m in a meeting and someone makes a point I hadn’t considered, I try to say “that’s a good point, I hadn’t thought about it that way” instead of immediately reframing their insight as something I already knew.
None of this feels heroic. It feels mundane and sometimes uncomfortable. But it compounds. Over time, the people around you — your team, your clients, your partners — learn that when you do express confidence, they can trust it. Your signal-to-noise ratio improves. Your opinions carry more weight precisely because you don’t offer them indiscriminately.
The Paradox
The paradox is clean and worth naming: the people who are most willing to say “I don’t know” are usually the ones who know the most. Because genuine expertise brings an awareness of how much you don’t know. It’s the intermediate practitioners — the people who have learned enough to feel competent but not enough to see the edges of their understanding — who are most dangerous.
I’d rather work with someone who knows three things deeply and admits the boundaries of those three things than someone who claims to know thirty things and can’t distinguish between their genuine knowledge and their comfortable assumptions.
Intellectual honesty is not a weakness. It’s the foundation that everything else is built on.