Insights & Perspectives

Arguments, not content.

Long-form thinking on strategy, go-to-market, AI adoption and why companies fail, written for people who have read enough consulting decks to be suspicious of them.

Reading is cheaper than a consultant. Up to a point.

When the reading stops resolving it, thirty minutes of structured framing usually will.

Editorial standard

What gets published here, and what does not

Everything on this page defends a single claim and shows the reasoning. That is the only editorial rule, and it rules out most of what passes for consulting content.

No listicles. "Seven ways to improve retention" is a format that guarantees at least four of the seven are filler, because the number was chosen before the thinking.

No borrowed frameworks with the sources stripped off. Minto, Porter, Lafley and Martin, Kaplan and Norton, Christensen, where their work is used it is named. Renaming a published framework and presenting it as proprietary is common, and it tells you what else the author might be comfortable doing.

No invented numbers. Where a figure appears it is sourced or labelled as an estimate with its assumptions attached. Where a number would be useful and is not available, that absence is stated rather than filled.

Arguments that could be wrong. A piece that nobody could disagree with has not said anything. Several of these take positions that a reasonable practitioner would contest, and the counter-argument is generally included rather than hidden.

Questions

About the writing

How often is new work published?

Long-form pieces land when there is an argument worth defending rather than on a content calendar. Shorter thinking goes out through the newsletter roughly every other week. Publishing on a schedule regardless of whether there is something to say is how good writing becomes filler.

Can I share or quote these?

Yes, freely, with attribution and a link. Sharing an argument internally is the most useful thing that can happen to it, several of these were written specifically to be forwarded to a colleague who needed the case made independently.

Is this written by AI?

The arguments, the positions and the judgment are mine. AI is used in the production layer here exactly as it is in client delivery (research assembly, structural drafting, editing passes) under review at every stage. Given that this practice sells AI enablement, being vague about that would be an odd position to hold.