Thought leadership isn't about having the right answers. It's about asking the right questions in public.

A commercial director with twenty years of experience in industrial B2B starts posting on LinkedIn. The first post is a list of tips on managing a sales team. So is the second. And the third. After three months, he stops — convinced he has nothing left to say.

The problem wasn’t a lack of ideas. It was a fundamental misunderstanding of what thought leadership actually means.

The most common mistake: confusing authority with omniscience

Thought leadership is one of those concepts that resists tidy translation. But the idea itself is straightforward: being the person your industry turns to when it wants to understand how things are changing, where things are heading, and what’s worth doing about it.

The trouble is that almost everyone interprets this role as needing to have the answers. So they wait until they have something definitive to say. They wait for the right moment. They only write when they’re one hundred percent certain.

The result: they never write at all, or they write so rarely that they leave no lasting impression.

The reality is different. The people who build genuine authority over time are not the ones who know everything. They are the ones who reason in public with consistency — who share their process, who aren’t afraid to say “I’m not sure yet, but here’s how I’m thinking about it.”

Reasoning in public: what it actually looks like

Take an HR manager at a mid-sized manufacturing company. She knows perfectly well that the technical skills shortage on the factory floor is a crisis: roles are going unfilled, young people aren’t coming through, and the existing workforce is ageing. She doesn’t have a solution. But she has a perspective — built over years of interviews, failed hires, and training programmes that didn’t quite land.

If she waits until she has a solution, she never writes. If instead she shares what she’s observing, what she’s trying, which hypotheses she’s testing — she becomes a voice. A credible voice, because the thinking is authentic and instantly recognisable to anyone living the same problem.

Reasoning in public doesn’t mean broadcasting uncertainty or appearing unprepared. It means showing the method, not just the result. It means saying: “Here’s what I saw, here’s what I thought, here’s what I changed.”

That structure — observation, interpretation, consequence — is far more valuable than any list of best practices. Because it’s falsifiable, it’s personal, and it’s genuinely hard to copy.

Editorial consistency isn’t discipline: it’s infrastructure

This is where the second major misconception hides. Consistency gets treated as a character issue. “I need to be more disciplined.” “I need to remember to post.” As if setting a phone alarm would fix it.

Consistency is actually an infrastructure problem. Professionals who publish regularly for years don’t do it because they have stronger willpower. They do it because they’ve built a system that reduces the friction between “I have an idea” and “I’ve published it.”

What does that look like in practice?

Keep a log of observations, not ideas

Abstract ideas disappear. Concrete observations stick. A sales professional who jots down “today client X told me the issue isn’t price — it’s implementation time” has material. A sales professional who writes “I should write something about the importance of trust in the sales process” has a vague intention.

The log can be a notes app on your phone, a drafts folder, a shared document. The format is irrelevant. What matters is the habit of capturing the concrete while it’s happening.

Separate production from publication

Anyone who sits down in front of a screen with the goal of “writing a post” is mixing two incompatible activities: thinking and communicating. The result is usually a piece of writing that’s neither one thing nor the other — too rough to be useful, too polished to feel alive.

It works better to split the process: one moment to gather and develop the thought (even just fifteen minutes, with a voice note or a rough written sketch), and another to shape it into a post. The two stages can be hours or even days apart.

Have a thematic framework, not a rigid content calendar

A content calendar with titles and dates locked in months in advance is almost always abandoned within four weeks. The world changes, your thinking changes, enthusiasm runs out.

More useful is having three or four recurring themes — the open questions of your profession, the unresolved tensions in your sector — and knowing that every post will land somewhere within them. This gives coherence without rigidity. It lets you respond to what’s current without losing the thread.

How long it really takes

A realistic figure: a professional publishing twice a week on LinkedIn, with considered rather than generic posts, invests between thirty and sixty minutes a week — at cruising speed, once the system is working. The first few weeks cost more, because the method is still being built.

Nine months. That’s the average time it takes for a professional with real experience and a clear point of view to start seeing tangible results: meaningful connection requests, invitations to speak, inbound leads, professional opportunities that arrive without being chased.

Nine months sounds like a long time. But it’s exactly the time that passes anyway — whether you publish or not.

The point of view is the product

Ultimately, thought leadership is not a format. It’s not a posting frequency. It’s not even a topic.

It’s the point of view. The ability to look at something familiar — a market, a function, a technology — and see it slightly differently from everyone else. And then say so, clearly and consistently, until that perspective becomes associated with your name.

The commercial director from earlier hadn’t run out of ideas. He’d run out of generic advice. He had months of material left, if only he’d stopped chasing definitive answers and started articulating the open questions he works with every day.

That was his real value. It had always been there. It was just waiting to be said in public.