Thought leadership without the ego

Good thought leadership is about the buyer's problem. Bad thought leadership is about the author.

Services firms publish a lot of the second kind. The founder's take on the future of AI. The managing partner's five predictions for the year. A white paper that's really a capabilities deck with more paragraphs. Buyers can tell, and they scroll past.

The ego test

Read your last piece and ask one question. Who's the hero?

If it's your firm, your framework or your partner's insight, it's ego. If it's a buyer in a specific seat working through a specific problem, it's useful.

The difference shows up in the first line. "At our firm, we believe..." is ego. "If you just inherited a migration plan that was scoped before you arrived..." is useful. The second one makes a buyer stop and think, "That's me."

What senior buyers actually read

They read things that help them make a decision they're facing this quarter. How to scope a data platform rebuild so the board doesn't kill it in year two. What to ask a vendor before signing a fixed-bid modernization. Where integration programs usually go sideways after an acquisition.

They read things written by someone who's clearly been in the room. Specific, a little blunt and honest about what goes wrong.

They don't read predictions. Nobody in a budget meeting has ever cited a vendor's prediction.

Write from the field

The best material is already in your firm. It's in the problems your delivery teams solved last month and the mistakes they watched clients make.

Ask your delivery leads one question each week. What surprised you on a project lately? Most of the answers are posts. A client that underestimated the data cleanup. A cutover that went wrong in a way nobody planned for. A team that moved faster once someone killed a weekly status meeting.

Strip out the client's name and details. Keep the shape of the problem and what you learned. That's thought leadership a CIO will forward to their team.

Teach the hypothesis

The strongest pieces do in public what your opener does in private. They name a common situation, say who it hurts and guess the problem underneath.

Say you sell modernization work. A post titled "The migration plan you inherited is probably too big" does the same work as a Hypothesis Opening, aimed at every new CIO at once. It's a research hook for a whole category of buyer.

And when your seller later writes to one of those CIOs, the post is proof you've thought about their situation before. The opener and the content back each other up. The method works the same way in both places.

Let people disagree

Ego hates being wrong in public. Useful content invites it.

End a post with your honest view and let readers push back. When a senior buyer comments that you've got it half right, you've just learned something about their world, and you've started a conversation with someone you couldn't have reached cold.

That's the same move as the binary exit in an opener. Make it easy to correct you.

Who should write it

The founder or senior partner should put their name on it. Buyers want to hear from the person who'll stand behind the work.

But they don't have to write every word. A good editor can turn a 20-minute conversation into a post. What matters is that the thinking is real and the voice sounds like a person, not a marketing department.

Publish less and make each piece count. One honest post a month beats four forgettable ones. More on making content earn its keep in content that sells services.

How you'll know it's working

You won't know from likes. You'll know when a buyer opens a first meeting with "I read your piece on inherited migration plans." You'll know when your sellers start sending posts to prospects, and prospects reply.

That's the only measure that matters for a services firm. Did it start a conversation with someone who buys?

Drop the ego, write about their problem and those conversations start showing up on their own.