(2026-08-19) Highsmith Practitioner Voice

Jim Highsmith frames Practitioner Voice. I've been called a Thought Leader. I don't love the term. But I've used it, because there wasn't another one.

(Martin Fowler's) feedback on my Wild West to Agile book was direct: put more of yourself in. I was holding back. I'd written a software history book when I had a memoir trying to get out. Martin saw the gap before I did.

What he was asking for had a character, a way of writing that neither of us named at the time.

Three ways to disappear

Thought leadership started as a real thing.

Then it became a content category. Then a marketing function

The academic route looked like the alternative. If you wanted to be taken seriously, you built the scaffolding. Citations. Caveats. Literature reviews. You buried the lead because that's what rigor looked like. You suppressed your own voice because the author wasn't supposed to show.

I've done versions of both

But from the beginning I kept looking for ways to stay in the frame

because I wanted their voices, not merely a summary of their ideas

The pressure to conform was real.

The problem isn't academic writing or thought leadership individually. At their worst, both do the same thing: they edit consequential human judgment out of the prose. The practitioner disappears behind the rigor or the polish, and what remains is correct but weightless.

Now a third option has arrived — LLM Voice — that doesn't require hiding at all, because there's no one there. That was a problem worth solving before AI arrived. Now it's urgent.

To come out of hiding, I propose a new writing category: Practitioner Voice.

Academic writing builds to the claim. Thought leadership makes the claim and explains it. Practitioner Voice starts with the claim and trusts the reader to close the gap. The author's judgment stays visible throughout. The whole piece organized around what the author has concluded from experience, not what the evidence might tentatively suggest.

Martin Fowler writes this way. His best pieces don't build to the conclusion, they open with it. The rest is a practitioner showing his reasoning, not constructing a case for a jury. The reader either recognizes the pattern from their own experience or doesn't. He doesn't write for the ones who don't.

Practitioner Voice is the thing only you can write, because it's built from what only you have lived.

Four things separate Practitioner Voice from the alternatives.

Authority from experience, not credentials.

Practitioner authority comes from having been in the situation, not as a researcher studying it, but as a person responsible for the outcome.

For consultants the authority takes a slightly different form. We rarely carry direct accountability for outcomes. But if we do our work well, we've been close enough to consequence, across enough contexts and enough years, that the pattern recognition is real.

Tension without resolution. Academic writing resolves tension — that's what conclusions are for. Thought leadership resolves it in the three takeaways. Practitioner Voice names the tension and leaves it live. The practitioner knows the tension is real and the reader has to navigate it themselves. Resolving it for them would be lying.

The author stays in. Academic writing never allows this. Thought leadership allows it only as personal brand. In Practitioner Voice the author's judgment is the point

The readership contract. Academics write for peer reviewers. Thought leadership writes for eyeballs. Practitioner Voice writes for people who recognize the pattern from their own experience. It's comfortable with limited context.

This isn't new behavior.

It's been building for a decade. Nobody called it anything. Without the category, there was no way to teach it, no way to recognize it, no way to say: that's the thing, do more of that.

Now AI produces competent writing at scale — fluent, well-organized, correctly structured, optimized to say nothing wrong. Call it what it is: LLM Voice. The most insidious failure mode of the three because it's indistinguishable from the real thing until you notice nothing is at stake.

AI can mimic the sound of Practitioner Voice. It cannot own the consequences behind it.

Practitioner Voice survives the current moment not because it's protected from AI, but because the thing it's made of — accumulated consequence-bearing experience stated plainly — has to be earned.

Naming the category is the first step. The craft — a guide to writing in Practitioner Voice — is my next contribution, which I will add to this article when it's ready.

cf (2016-04-15) Book Review Donald Schon The Reflective Practitioner