article 5 min read

Founders don't have a voice problem

9 August 2026


Ask a founder or a chief executive what they know about their market that nobody else does.

You get one of two answers.

Sometimes it is startlingly specific. A pattern they have watched play out across forty sales calls. The thing customers say once the formal part of the conversation is over. The reason the obvious solution keeps failing, which only becomes visible after you have shipped it twice. When you get that answer, everything downstream becomes easy. The positioning is already there. The posts more or less write themselves.

More often you get a paragraph containing six abstract nouns.

Innovation. Transformation. Partnership. Trust. Simplicity. Growth.

That paragraph is almost always diagnosed as a communication problem, and the remedy prescribed is more communication — a content calendar, a ghostwriter, a posting cadence, a more human tone, a personal brand. I have watched executives publish diligently for a year on that basis and arrive at the end of it with roughly the authority they started with.

The six nouns are not a writing failure. They are an unfinished piece of thinking, and production does not finish it.

Frequency is not accumulation

The failure modes are consistent enough to list.

Posts get written to fill a calendar rather than to develop a position. Ghostwriting reproduces a generic executive register instead of preserving the way a particular person actually argues. The organisation’s research and customer evidence sit in one place while the founder’s commentary happens somewhere else, and the two never meet. Engagement figures shape the next post without ever reaching the underlying argument.

The result is frequent publishing that does not accumulate into anything.

Authority accumulates when each piece strengthens, extends or tests a position that already exists. Volume on its own just restates. Twelve months of competent posts built on six abstract nouns produces twelve months of competent posts, and a founder who is no more credible on their subject than they were in January — because nothing was ever being built.

Three questions

The useful diagnostic is not “what should we post about”. It is three questions, in order.

What do you know that other people in this market do not? Most founders can answer this, given time and a decent interviewer. The answer is usually a story rather than a claim, and it usually has to be excavated — it lives in sales calls and support threads and the founder’s own head, and it has never been written down in a form anyone else could use.

Which of your claims are supported, and which are assumptions you have been repeating? Far fewer can answer this. The two categories tend to have merged, because a claim repeated confidently for eighteen months starts to feel like something the company has established. Separating them is uncomfortable and it is most of the value.

What would change your mind? Almost nobody volunteers this one, and it is the one that matters most.

The opposite problem

There is a second failure, and it is the more interesting of the two because it looks like success.

Founders are selected for conviction. Investors reward it, teams need it, and the job is genuinely impossible without it. Meanwhile the market gives an honest signal about what travels: a narrative with thin evidence behind it travels extremely well, and evidence with no narrative around it barely travels at all.

So the founder who solves the first problem walks directly into the second. The position gets sharp. It starts working. People repeat it back. And then, quietly, it stops being informed by evidence and starts selecting it.

You can hear it when it has happened. We’re customer obsessed. The transformation is working. Our customers love us, the churn is a pricing issue. Each of those may have been earned once. What makes them dangerous is that new evidence no longer tests them — it gets sorted into things that confirm the story and things that can be explained away.

The failure has a name: narrative capture. Once a leader becomes associated with a particular belief, contradictory evidence starts getting discounted, because changing the story now carries a reputational cost that holding it does not.

The narrative that was an achievement has become a filter.

Strong enough, and porous

Which gives the actual objective, and it is harder than either failure suggests.

Build a narrative strong enough to create understanding, and porous enough to be changed by evidence.

Most advice covers the first half. The second half has a practical test, and it is the third question above: say in public, in advance, what would cause you to abandon the position. Not as humility — as specification. We believe mid-market finance teams will pay for this because of what we have seen in thirty implementations; if the next ten look different, we are wrong about the segment rather than the message.

A position with its own disconfirming conditions attached cannot quietly become a filter, because it has already told everyone what would break it. It also happens to be far more persuasive than certainty, for the reason set out in Name the evidence you don’t have: a reader who can see you marking the limits of your own claim stops discounting the rest of it.

The founders whose narratives are worth listening to are not the ones with the most conviction, or the best turn of phrase, or the most consistent posting schedule.

They are the ones who know something specific, can tell you what it rests on, and can tell you what would change their mind.

That is not a voice problem. It is a synthesis problem, and it is worth solving in that order.

Topics

editorial-intelligencenarrativesevidencethought-leadership

What to explore next

See how the ideas in this Field Note connect to the frameworks, diagnostics and workflows in Editorial Intelligence OS.

Explore the EI OS →

Keep in touch with Editorial Intelligence

Occasional updates on new research, findings and ways to take part.

No spam. Unsubscribe in one click.

Your address is used only to send these updates. Read the privacy policy.