Perspectives

The Curse of Knowledge

By Robert Johns

There’s a pattern I keep seeing in hard tech.

A company builds something genuinely breakthrough — a new approach to manufacturing, a novel sensor architecture, a defense capability that didn’t exist two years ago. The engineering is world-class. The physics are real. They’ve raised capital, hired a team, and started selling.

But somewhere along the way, the pitch stopped working as well as it should.

The website reads like a technical manual. The sales deck answers questions nobody’s asking yet. The founder can explain the technology in extraordinary detail but can’t explain why it matters in one sentence. A prospect sits through a 45-minute demo and walks away impressed but unable to explain what they just saw to their CFO.

Nobody planned for this. It happened gradually. A founder I spoke with recently realized that over the course of several years, his company’s external materials had slowly drifted from telling a clear story to listing specifications — and nobody on the team had noticed. Why would they? Everyone inside the company already understood the value.

This is the curse of knowledge. And it’s quietly costing technical companies contracts, capital, and talent.

How It Happens

The curse of knowledge is a well-documented cognitive bias: once you know something, you can’t un-know it. You lose the ability to imagine what it’s like to encounter your idea for the first time.

For most businesses, this is a minor nuisance. For deeply technical companies, it’s an operational liability.

When you’ve spent three years developing a novel approach to carbon capture or a new architecture for autonomous systems, the technology becomes self-evident to you. Of course it works this way. Of course this is the breakthrough. You’ve internalized the logic so completely that you skip past it when you communicate — the same way a native speaker can’t hear their own accent.

So the deck starts leading with architecture diagrams instead of the problem you solve. The website lists twelve capabilities when the buyer only cares about one. The sales conversation becomes a tour of how it works instead of an argument for why it matters. Every surface of the company starts speaking the language of the people who built it rather than the people who need to buy it.

And the most dangerous part: nobody inside the company can see it happening. Because to them, it all makes perfect sense.

Three Languages, One Room

In most early-stage technical companies, there are at least three internal languages competing for control of the narrative.

Founders speak in vision. They paint the big picture — the market opportunity, the long-term trajectory, the world that exists once this technology wins. This is how they raised capital.

Engineers speak in precision. They want to describe exactly how something works, down to the architecture and the edge cases. This is how they build trust with each other.

Sales speaks in urgency. They want to compress everything into a pitch that creates momentum before the prospect’s attention runs out.

All three are valid. None of them are what the buyer needs to hear.

Because buyers — especially in defense, critical infrastructure, and enterprise — think in risk, liability, and downside. They’re not asking “how does this work?” They’re asking “what happens when this fails?” and “can I defend this purchase to my procurement board?” and “will this vendor still exist in three years?”

A program manager at a defense prime who champions your product over the incumbent isn’t making a technology decision. They’re making a career decision. If it works, they’re a visionary. If it doesn’t, they chose the startup over Lockheed and now they have to explain why. There’s a reason “nobody ever got fired for buying IBM” has survived as a saying for fifty years — it captures something true about how large organizations actually make purchasing decisions. Your narrative has to give that person the language to defend the purchase internally — not just to understand it, but to sell it up the chain.

When the narrative is fragmented — when the website says one thing, the sales deck says another, and the founder tells a third story on a podcast — the buyer doesn’t pick the version they like best. They hear noise. And noise, to a risk-conscious buyer, sounds like uncertainty. It sounds like a bet they can’t justify.

The result is a company that insiders describe as a “best-kept secret.” That phrase feels like a compliment. It’s not. It’s a diagnosis.

Naive Eyes & An Empty Chair

Here’s the counterintuitive part. The person best equipped to diagnose this problem is usually the person who knows the least about the product.

Not because ignorance is a virtue, but because for a brief window, an outsider sees your company exactly the way a cold prospect does — with no context, no assumptions, and no emotional attachment to the way things have always been described. They can hear the accent.

That initial perspective is a depreciating asset. The more you learn about the technology, the more you start to sound like the people who built it. Which is why it has to be captured quickly and translated into something durable — a narrative core that the entire company can align around, from the pitch deck to the website to the trade show booth.

But the diagnosis is only the beginning. The harder problem is maintaining that perspective over time, because the drift that created the problem in the first place doesn’t stop. The product evolves. New features ship. The team grows. The founder does a podcast and describes the company differently than the website does. Without someone actively maintaining the narrative — pressure-testing every new piece of collateral against how a cold buyer would actually experience it — the drift starts again within months.

Jeff Bezos famously kept an empty chair in meetings to represent the customer. It worked because it was a constant reminder that the most important person in the room was someone who wasn’t there. Technical companies need the equivalent for their narrative: someone whose permanent job is to keep asking “would the buyer understand this?” long after everyone inside the company has stopped being able to ask that question honestly.

This isn’t about dumbing things down. The technical depth still matters. But it has to be structured so the buyer can enter on their terms, not yours. The first sentence has to answer “why should I care?” before the second sentence explains how it works.

Test It Yourself

You don’t need to hire anyone to find out if this problem exists at your company. Try this:

Hand your pitch deck to someone who has never heard of you and ask them to read it without commentary. When they’re done, ask them two questions: what do we do, and why does it matter?

The gap between what they say and what you wish they’d said is your narrative debt. Every company has some. The question is whether yours is a crack in the foundation or a cosmetic scratch.

If the person can parrot back your tagline but can’t explain the problem you solve, your narrative is shallow. If they can describe the technology but not the buyer, your narrative is inverted. And if they look up from the deck and say “I’m not sure what this company actually does” — that’s not a branding problem. That’s a revenue problem.

Originally published on X. Follow Robert Johns.

Work With Us

Whether it’s a logo, a website, a film or the whole brand, we’re here to help.

Contact

A person working at a desk, seen through reeded glass