All Perspectives › Writing = Thinking × Wording

You open AI to improve a sentence. Ten minutes later, it has changed the argument.

That can be useful. It can also mean that the most important decision in AI-assisted writing, what AI is allowed to shape, was never really made.

I kept catching myself doing exactly that. I knew what I wanted from the piece, but not always whether I wanted AI to improve the thinking, the wording, or both. The process could be productive, but it could also become a blur of better ideas, better sentences and unexamined hand-offs.

So I went looking for a simple way to make that division of labour visible before I write, notice when it shifts while I work, and learn from it afterwards. That search became the Thinking × Wording Lens.

If this sounds familiar, open the Lens now and keep it beside this article. Pick a position that feels plausible for something you are working on. Then read on. The interesting part is not where you start, but what the map reveals as the work moves.

What AI has pulled apart: Writing = Thinking × Wording

Writing has always involved at least two jobs: deciding what to say and finding the words to say it. They often happened so closely together that we treated them as one activity. Generative AI makes it possible to separate them much more explicitly.

You can bring the observation and judgement while AI helps formulate the prose. You can use AI to challenge your thinking and still write every sentence yourself. You can develop both together, or set a task and let AI carry most of both. All are truthfully “using AI”, which is why that phrase tells us very little.

“The useful distinction is not one scale of AI-ness. It is two variables: where the thinking comes from and where the wording comes from.”

Even a perfect AI scanner could not tell you whether AI polished sentences, challenged an argument, opened a research path or supplied most of the thesis.

That raises a related question I have been circling in earlier Perspectives: perhaps authorship is becoming a more useful way to talk about the value of a piece than the old shorthand of who “wrote” it. Authorship is not a percentage. It is the presence of an essential contribution. The Lens does not measure authorship, but it can help make the provenance of that contribution visible: in the thinking, the wording, the direction, the judgement, or across the process.

Download this Perspective
PDF · designed for reading, saving or sharing

Download PDF

Why × and not +

The multiplication sign is deliberate. In one important sense it is mathematical: if either thinking or wording is zero, the outcome is zero. No substantive thought means there is nothing worth carrying; no wording means nothing reaches the reader.

I am not proposing a numerical quality formula. The point is interdependence. Polished wording cannot rescue empty thinking, and strong thinking cannot travel without usable words.

The mapping

I chose three positions on each axis rather than a binary human-or-AI split because the middle matters. Thinking and Wording can each be Mainly human, Developed together, or Mainly AI. Put those together and nine positions appear, with Thinking on the horizontal axis and Wording on the vertical. “Together” means substantive contribution from both. It does not mean a 50/50 split.

THINKING →
WORDING ↓
T1
Mainly human
T2
Developed together
T3
Mainly AI
W1
Mainly human
T1W1
Mainly human
T2W1
Think Collab
T3W1
Human-articulated
W2
Developed together
T1W2
Co-worded
T2W2
Interplay
T3W2
Human-edited
W3
Mainly AI
T1W3
AI-worded
T2W3
AI-expressed
T3W3
Mainly delegated

The codes are coordinates, not grades. T1W3 means mainly human thinking with mainly AI wording; T3W1 means the reverse. The question is not which square sounds most virtuous. It is which combination fits this particular work, and why.

The map describes provenance, not quality. Mainly human work can be poor; Mainly delegated work can be entirely fit for purpose. AI-worded content can help expertise travel faster or flatten distinctive thinking. Human-edited AI thinking can be useful for synthesis or make weak reasoning look more convincing. The map makes those choices discussable. It does not make them for you.

The position belongs to the work, not the writer

You are not a T1W2 or T2W2 “type”. A position describes a piece of work, or even a phase of it. A draft may start with mainly human thinking, move into developed-together thinking when AI surfaces a useful angle, then return to mainly human wording for the final voice. Movement is normal.

Before, during and after

Let’s say you are writing a CEO point of view. Before you start, you decide the judgement and conclusion should remain mainly human, but you want AI to challenge assumptions, so you aim for Think Collab: thinking developed together, wording mainly human. During the work, AI surfaces an angle that changes the argument and then starts helping substantially with the phrasing, so the piece moves towards Interplay. Before publishing, you map where it actually ended up and ask whether that still fits the purpose. If not, you change the process or rewrite. The value is not staying in one square. It is noticing, choosing and being able to explain the choice.

“The value is not staying in one square. It is noticing, choosing and being able to explain the choice.”

For teams, clients and agencies

The Lens becomes more useful when work involves more than one person. Before arguing about tools, a team can discuss the division of labour: which content deserves mainly human thinking, where developing together helps, where AI-led wording is efficient, and what guardrails follow. Different content types can legitimately lead to different answers.

“AI makes us more efficient” is incomplete until we agree what is becoming more efficient: routine wording, research, or judgement and strategy.

The Lens does not decide fees, scope or responsibilities. It can make the underlying bargain explicit first: what is the client buying, which human contribution remains part of the value, what can AI accelerate, and what still deserves human review?

A boundary: you need access to the process

This is not a forensic tool for judging a stranger’s finished prose. I can map my own process, or one I share with a colleague, client, agency or partner, because the people involved know what happened. Looking only at somebody else’s final text, I usually cannot know where either the thinking or wording substantially came from.

That is one reason I prefer this to scanner-policing. It asks participants to make the process visible rather than pretending provenance can be reverse-engineered from fluent prose. Without access to the process, the honest answer is: we do not know.

A lens, not a verdict

The Thinking × Wording Lens maps provenance, not quality. It is not a detector, rating, certification, compliance checklist or disclosure standard. A T1W1 piece can be poor; a T3W3 piece can be entirely fit for purpose. Accuracy, ethics, confidentiality, legal obligations and disclosure still require their own judgement.

This Lens isn’t finished. I’d like your hand in it.

I built it for myself first, and I am publishing it before pretending it is finished. A small international Feedback Circle has already sharpened it. Their recurring challenge: prove the practical value, avoid turning it into a lower-is-better AI percentage, and allow real processes to move.

One question remains open: is this useful beyond five minutes of self-reflection? I think the answer lies in the decisions it enables for specific content, teams and client relationships. I would rather test that in public than declare it solved.

So I would like fellow content creators to push against it. Where does the map break? Which labels mislead? Which cases would make it more useful? I will fold what I learn into successive versions, with reasoned decisions and credit where contributors want it. The framework is CC BY 4.0.

Explore the live Lens at bertvanloon.com/txwx/.

The Open Lab will follow as a public place to challenge, improve and add real cases. Open to contributions. Curated by Bert. Improved through iteration.

Download this Perspective
PDF · designed for reading, saving or sharing

Download PDF

All Perspectives › The Meaning of Efficiency and Four Other Questions We Should Ask Before Using AI

Over the very hot summer, I spoke with over a dozen agency leaders and experts about AI, and what leads the conversation about how to use it. Not about models, features or whether agencies should use it. That ship has sailed. I was interested in something closer to their daily reality: what is becoming central in the conversations they have with clients about using AI? One answer came back remarkably often, and practically always first in line: efficiency.

It makes sense, in a way. Agencies are finding ways to research faster, develop first drafts faster, produce variations faster and automate work that previously consumed expensive human hours. Clients know this too. So a perfectly reasonable commercial question follows: if AI makes the work more efficient, who benefits from that efficiency?

But something interesting happened when I kept asking what efficiency in this context actually meant. The answers became less precise. Not because these people had not thought seriously about AI. They had. It was because a seemingly concrete word turned out to hide quite a few different questions.

Efficient at what?

Suppose AI saves three hours. Sounds good. But three hours of what? Research, exploring ideas, developing an argument, writing a first draft, editing, translation, producing fifteen variations or moving copy through approval? Those are not always interchangeable hours.

Saving three hours of repetitive adaptation may free a senior strategist to spend more time understanding the client’s problem. Saving three hours by shortening that understanding process might achieve exactly the opposite. And then there is another, million-dollar-or-more question: efficient for whom? The agency may save time while the client gets the same output for the same price. The client may expect the saving to be reflected in the fee. A team may use the saving to produce more. Or everyone may simply fill the liberated hours with more meetings.

“Saving three hours isn’t value yet. What happens to those three hours is.”

Efficiency, in other words, is not the end of a conversation with one homogeneous meaning. It should be the beginning of a value conversation.

Download this Perspective
PDF · designed for reading, saving or sharing

Download PDF

Every gain can hide a loss

That became clearer in those agency conversations when we moved beyond the first answer. We tend to name what we want to gain without naming what we might lose in getting it. Faster research sounds attractive, but not if it produces shallower understanding. Faster writing sounds attractive, but not if the efficiency comes from removing the thinking that made the piece worth reading. Cheaper production sounds attractive, but not if the client was actually paying for expertise, judgement and a point of view rather than the physical production of 1,200 words.

“We want AI to increase X without sacrificing Y.”

That sentence makes “we want to use AI for efficiency” suddenly insufficient. We might want AI to reduce production time without reducing the strategic thinking the client is paying for. Or make research faster without making our understanding shallower. Or reduce routine work so people can spend more time on work where human judgement matters. Now we are having a useful conversation.

There is a useful precedent here. Digital tools have never created only one kind of value. Some made work possible or better in ways that changed the craft itself. Think Photoshop or Procreate. Others made an existing level of output easier, faster or accessible to many more people. Think Canva, or more recently tools such as Jasper. The boundaries are not clean, and the products keep evolving, but the distinction matters: technology can improve the work, improve the economics of the work, or do both.

Once I started pulling efficiency apart this way, another question began bothering me: why are we assuming efficiency is what we want from AI in the first place?

Five peas, different destinations

There are already excellent inventories of what marketers can do with AI. We do not need another list of 50, 100 or 230 use cases. The question I find more useful comes one step earlier: what are we actually trying to improve by bringing AI into this work? I currently see five closely related questions. Five peas in the same AI pod, perhaps, but each can lead the work in a different direction.

The askThe advantagePotential hidden trade-off
EfficiencyWhat should become easier?Less time, cost, effort or friction.Depth, judgement or valuable human time gets cut with the waste.
QualityWhat exactly should become better?Clearer, sharper, more accurate, useful or consistent work.Polish disguises weak thinking or erases a recognisable voice.
ExplorationWhat do we want to see that we might otherwise miss?More alternatives, perspectives, questions and counterarguments.More possibilities become noise, convergence or outsourced judgement.
ScaleWhat becomes worth doing because AI makes more possible?More markets, formats, audiences or versions become practical.Errors, sameness and mediocrity scale with the output.
LearningWho should become better afterwards?Stronger human understanding, skill and judgement.A better immediate output leaves the human less capable.

The categories are deliberately simple. The same task can serve several of them. Research, for example, can become faster, better, more exploratory and more educational at the same time. The point is not to force every use case into one box. It is to make the intended gain explicit enough that we can also see what deserves protection.

Before you invite AI in

This does not need another elaborate framework. Before using AI for a meaningful piece of work, ask three questions: what are we trying to achieve? Which gain matters most here: efficiency, quality, exploration, scale or learning? And what are we unwilling to sacrifice to get it?

A CEO perspective might be designed primarily for exploration, using AI to challenge assumptions and expose alternative interpretations while explicitly protecting human ownership of the eventual argument and voice. Once that perspective is finished, using AI to adapt it for several markets may be primarily about scale, while protecting factual accuracy and the meaning of the original.

Same person, same AI, even the same original piece of content, but a very different reason for inviting AI in and therefore quite possibly a very different way of using it.

The other half of the brief

The conversation about AI has understandably spent a lot of time on capability: can it do this yet? Increasingly, the answer is yes. The more useful question now may be what we want that capability to improve. Efficiency is a perfectly good answer. So are quality, exploration, scale and learning. But naming the gain is only half the brief.

The other half is naming what must survive the improvement. Faster without shallower. Better without blander. More without multiplying mediocrity. Broader exploration without outsourcing judgement. More help without less learning.

“The workable idea: every AI ambition needs two answers. What do we want to gain, and what are we unwilling to lose to get it?”

That may be a more useful starting point than asking how much AI we should use. Because the value of AI is not in how much human work it can remove. It is in what becomes better when we choose, deliberately, what should change and what should remain human.

Download this Perspective
PDF · designed for reading, saving or sharing

Download PDF

All Perspectives
›
We Are Content Creators First, Second and Third. Marketers Somewhere After That.

I have said that line to a lot of rooms full of content people: “We are content creators first, second and third. Marketers somewhere after that.” It is deliberately overstated. What bothers me is how few fellow marketers look offended.

Most of us came into this profession because we love ideas, stories, writing, video, editorial thinking, formats, craft. So that is what we got good at.

We built editorial calendars, production processes, content operations, increasingly sophisticated workflows. And then, usually somewhere near the end, somebody would ask what we were going to do with the thing now that it was finished. Which channels? Any paid budget? Who is posting it on LinkedIn?

A few years ago, Content Marketing Institute asked for my input for its annual trends update on where content marketing budgets were being wasted. I said over-creation and under-distribution, and reduced it to four words: less content, more marketing. I sometimes joke that we should have called the discipline marketing content instead. It is only a joke because there is enough truth in it to sting.

Download this Perspective
PDF · designed for reading, saving or sharing


Download PDF

Since then, I have realised my diagnosis was too narrow. Distribution is only the visible half of the problem.

I have been drawing the whole thing on whiteboards for years as a shelf. Content is the row of books in the middle. Marketing is the two bookends holding it upright, one at each end. But bookends as most people picture them are flat and closed. Marketing turns up, props the work in place, and leaves.

So, I draw mine with a porch. An open, covered space on the inside face of each bookend, where the two disciplines are meant to sit together for a while.

The front porch is where marketing comes in before anything is made, and it brings two things. One is the business objective the content exists to support: what needs to change in the market, in someone’s mind, in behaviour, preference, demand or retention. The other is what we know about the audience, arriving early enough to shape the content rather than to approve it. Between them they answer the question we skip most reliably: why should this particular thing exist at all?

The back porch is where marketing supports the finished work on its way out: how the idea finds those people, how it behaves in the environments where they meet it, and what should happen once they have consumed it.

Most content operations have the bookends. Almost nobody builds the porches. Marketing arrives at the last minute, holds the work upright long enough for it to be published, and goes home.

“Marketing should not begin when the content is finished. It should decide what deserves to be created.”

The bottleneck moves

Then AI arrived, and at first it looked like it would make the imbalance permanent. Research moves faster. Drafts get challenged and improved. One idea becomes five formats. A team of three produces what used to take twelve.

All of which matters less than it sounds, because the part of the job we were already best at is the part that just got cheaper. When your strongest muscle gets a machine attached to it, the relative value of your weakest one goes up. We can now produce more content, but audiences did not acquire more hours in the day. We can publish in more places without understanding any of them better. We can generate an impressive volume of perfectly competent material without getting any better at deciding what deserves to exist.

“The bottleneck moved, and most of us are still standing at the old one.”

Make AI your difficult client

Here is the part I did not expect.

I spent two years worrying that AI would become another excuse to make more content. It still might. But the same technology is also the first practical way I have found to force marketing thinking into the process before anything gets made. Not by asking AI to be the marketer, which it cannot be, but by giving it the one role content teams systematically avoid.

Make it the difficult client. The one who refuses to nod politely, does not care how much work you have already put in, and keeps asking why.

Before you ask AI to research anything or draft anything, give it the actual brief: the business problem, the audience, what you know about them, what you believe needs to change, what evidence you have, where you expect resistance, which channels matter, and what outcome would make the work worth doing. Then tell it to interrogate you, not to help you.

My own prompt is three words: roast my idea. The feedback stings, but considerably less than publishing something nobody finds, reads or remembers. What comes back is the set of questions we are best at skipping:

  • Are we solving a real audience problem, or filling the calendar?
  • What assumption are we making about these people that we have not tested?
  • Why would they care about this now?
  • Is content even the right response?
  • What would have to be true for this to work?

The obvious objection is that a model knows nothing about your market, so its challenge is worthless. That objection misunderstands where the value is. It does not come from the model’s knowledge. It comes from yours, extracted under pressure.

A brief written for a colleague survives on shared context: everyone in the room already knows who the customer is, so nobody writes it down, and nobody notices it was never decided. A brief written for something with no shared context cannot hide in that gap. You have to state the audience, the change you want, and the reason this thing should exist, in words, in a specific order. Half the time you discover you cannot. That is the finding. AI cannot supply market truth that was never there, but it is unusually good at making you confront what you failed to specify, and it will do it at eleven at night, twelve times, without getting tired of you.

“

It does not come from the model’s knowledge. It comes from yours, extracted under pressure.

Keep the client in the room

The brief does not have to disappear once creation starts. Most of the damage happens after it: the piece drifts towards what interests us rather than what matters to the reader, the useful part ends up halfway down the page, we start assuming knowledge the audience does not have. Feed the marketing intent back in as the work evolves and ask whether it still serves the problem you identified. That is a different use of AI from asking it to make a paragraph punchier.

It changes the other end too.

A LinkedIn post is not a shortened article. A newsletter is not a dumping ground for whatever appeared on the website that week. A conference talk is not a blog post with slides. Yet the single most common use of AI in content teams remains mechanical: turn this article into five LinkedIn posts. That is not distribution. That is photocopying.

“That is not distribution. That is photocopying.”

Give AI the original marketing objective and the context of the channel instead, and ask which part of the idea deserves to travel there, what would have to change for it to work in that environment, whether the audience you want is even present, and what somebody should be able to do next if the idea earns their attention. Those are marketing decisions. Some belong on the front porch before the work is made; others belong on the back porch before it goes out into the world. None belongs in a last-minute export menu.

And once something is published, the same difficult client is useful again: which framing attracted the audience you actually wanted, which questions kept recurring, what produced a spike and nothing else, what deserves another iteration, and what should quietly be allowed to die. That is not reporting. It is the next brief, arriving early.

The muscle we keep training

Which brings me to what bothers me most about how our profession is currently learning AI. We gravitate towards using it on the part of the job we already know. Writers learn AI writing. Video people learn AI video. Content teams learn to produce, adapt and repurpose faster. Of course we should learn those things.

But content creators should spend less of their AI-learning time becoming faster at content creation, and more of it becoming better marketers.

I have argued for years that this industry needed less over-creation and more marketing. The fix, it turns out, may involve the greatest content-production accelerator anyone has ever handed us — pointed at the brief as often as the draft. It can sit on either porch with us, keep asking why, and make it much harder to hide the marketing questions we failed to answer.

Maybe AI will not just change how we make content. Maybe, finally, it can help us put the marketing back into content marketing.

Download this Perspective
PDF · designed for reading, saving or sharing


Download PDF

All Perspectives
›
AI Content: Don’t Ask How Much AI Is in It. Ask How Much of You Is.

Writers are now deliberately making their writing a little worse to prove they are human.

Roughing up a clean sentence. Leaving in the em dash they would normally cut. Adding a small stumble on purpose, so nobody suspects AI touched the work.

That is when I started wondering whether we are asking the wrong question. Was it written by AI? Assisted? Edited? Would a detector catch it? All reasonable-sounding questions, and all getting us remarkably little further.

Perhaps the more useful question is not How much AI is in the work? but How much of you is in it?

Ann Handley recently approached this mess from a wonderfully pragmatic direction. Her question is not how to make our work look more human, but what we should consciously not hand over because doing it ourselves helps us think, develop taste, grow or simply gives us joy.

I like that question because it makes a distinction we easily lose in the efficiency debate: sometimes the process produces more than the output. But it also leaves me wondering about another part of the same puzzle: when we do use assistance, what makes the resulting work meaningfully ours?

“Sometimes the process produces more than the output.”

Substantial outside help in creating something is hardly new. Plenty of highly acclaimed creative work has been made with technology, collaborators, assistants, specialists and editors. We have simply become unusually anxious about one particular new participant in that process.

Download this Perspective
PDF · designed for reading, saving or sharing


Download PDF

Take iconic rock band Queen. For years their album sleeves proudly carried some version of “No Synthesizers.” That sounds like a declaration of technological purity, except Queen were anything but purists. They layered guitars and voices, manipulated tape and pushed recording technology hard enough to create sounds people sometimes mistook for synthesizers in the first place. Technology was all over the work. Their boast was really about where the remarkable part came from.

Famous painters make the same question more interesting. Raphael and Rembrandt worked with assistants and workshops; Andy Warhol turned his Factory into something that deliberately blurred the line between artist, studio and production system. The master’s own hand could be absent from substantial parts of a work carrying the master’s name. Yet we don’t automatically conclude that it therefore isn’t a Raphael, a Rembrandt or a Warhol. We look at conception, direction, choices and judgement, and sometimes argue vigorously about where assistance became authorship.

During my years in book publishing, I saw the same ambiguity much closer up. The work of highly individual literary authors could benefit enormously from editors who challenged, cut, reordered, questioned, suggested and occasionally saved a manuscript from its author. Nobody seriously concluded that the author’s name should therefore disappear from the cover. The famously fraught collaboration between author Raymond Carver and editor Gordon Lish shows how difficult that boundary can become, even without technology anywhere in sight.

That history matters because assistance, by itself, does not make a work less yours. Interchangeability does.

“Assistance, by itself, does not make a work less yours. Interchangeability does.”

If virtually anyone could have given the instruction and received essentially the same result, there may not be very much of you in it, however confidently your name sits at the top.

Generative AI makes this old question unusually visible because it can participate almost anywhere in the process. It can check a fact or improve a sentence, but it can also challenge an idea, build an argument, suggest examples, restructure a draft or generate most of the finished prose.

“Did you use AI?” therefore tells us remarkably little about what actually happened creatively.

I’m not sure “How much did you make yourself?” gets us much further either. Even if creative contribution could somehow be expressed as a percentage, would something that is 90% directly produced by you necessarily be more yours than something where your visible contribution was 10%?

One essential observation, connection or creative decision can be the reason an entire work exists. Conversely, you can personally type every word of something while contributing remarkably little that is distinctive.

Authorship is not a percentage. It is the presence of an essential contribution.

“Authorship is not a percentage. It is the presence of an essential contribution.”

So I find a counterfactual test more useful: would this particular thing have existed without you?

Not merely because you typed the prompt that caused an output to appear, but because you brought an observation, perspective, intention, direction, choice or judgement without which what is distinctive about this work would not have emerged.

But there is a catch. If what matters is what you bring, then we also need to keep developing what we are capable of bringing.

Robert Rose recently gave that risk a name that deserves to stick: formative debt. When AI lets us skip the awkward, repetitive and sometimes frustrating work through which experience, taste and judgement develop, we may get the output without building or maintaining the capability that allows us to judge it and make a distinctive contribution to it.

AI can make that comfort trap remarkably attractive: convincing output can arrive before we have done enough thinking to know whether it is actually good. If we repeatedly outsource precisely the work through which judgement develops, we may eventually have less and less of value to bring ourselves.

“

Convincing output can arrive before we have done enough thinking to know whether it is actually good.

Which also brings me back to Ann’s point. If part of the struggle is where we discover what we actually think, handing it over may remove something more valuable than the hours we save. But the reverse can be true too. Assistance can help an idea become more fully what its creator intended. An editor can sharpen it. A collaborator can challenge it. Technology can make something possible that craft alone could not. AI can expose a weakness, connect thoughts, test an argument or find a form for something that might otherwise have remained inside your head.

That leaves honesty. We should be open about assistance where that assistance materially matters, but honesty does not require a purity contest in which every contribution by another person or a machine somehow subtracts from the creator.

And then there is the test that all this creator-focused discussion can make us forget: the audience.

A lovingly handcrafted article can be pointless. Something produced with extensive human and technological assistance can make someone stop, reconsider an assumption, solve a problem or carry an idea into their own work.

The audience doesn’t consume the purity of your process. It encounters the result.

“The audience doesn’t consume the purity of your process. It encounters the result.”

So perhaps the useful test is simpler. Here is the practice I would offer, and it takes about ninety seconds. Before the outline, before the prompt, before the draft, write one sentence:

What do I bring to this that makes it mine and worth the reader’s attention?

Not the topic. Not the angle. The thing that would be missing if someone else, or something else, produced a piece on the same subject. An observation nobody has made out loud. A pattern you noticed because of where you have worked. A position you are willing to be wrong about in public.

If you cannot write that sentence, you do not have a piece yet. You have a topic. Everyone has topics.

If you can, keep it visible while you work and use anything you like. Use the editor. Use the workshop. Use the technology. Use AI wherever it genuinely helps.

Then, at the end, read the finished thing against that one sentence. Is it still true? And is the result worth someone else’s attention?

If it is, your essential and valuable contribution survived the process, however much help it took.

If it quietly stopped being true somewhere around the third draft, you have produced something efficient and interchangeable, and no disclosure statement will fix that.

Download this Perspective
PDF · designed for reading, saving or sharing


Download PDF

All Perspectives › I Think We Got the AI Arrow Backwards

For the first few years of generative AI I talked happily about AI-empowered professionals. Give capable people AI and they become more capable: faster researchers, better writers, more productive consultants, sharper marketers.

I’ve changed my mind about which way that sentence should run.

Not because it’s wrong. AI really does make people more capable. But the sentence starts in the wrong place. It starts with the technology arriving and asks what it does to us. The more useful question is what we hand it before it does anything at all.

Take the demo everyone has already run. Five friends each open the same AI assistant — Claude or ChatGPT, say — and ask it to plan a reunion trip to Rome. They end up with five different plans, ranging from genuinely good to unusable. Much of that difference will sit on the human side of the exchange: what they asked, what they told it, what they challenged, what they accepted.

The phrase human-empowered AI is decoration unless I can say what a person contributes that the system cannot simply supply for itself. At least four things come to mind.

The first is the problem. Not the request, the problem. The model receives what you typed, which is rarely the thing you actually need solved. Someone has to make that conversion, and it isn’t a prompting technique.

The second is context that the model cannot know unless you bring it: which constraints are real and which are negotiable, what somebody said in the room, why the obvious approach failed here two years ago.

The third is a standard. A model will produce a plausible answer to almost anything. Deciding whether a plausible answer is a good one requires a picture of quality you brought with you. If you don’t have that picture, you can keep accepting fluent work indefinitely.

And the fourth is accountability. When the output goes out under your name, you own it. That cannot be delegated to the thing that produced it.

AI can help us articulate the problem, surface relevant context and challenge our standards. But none of those can simply be assumed to come from the model. They are part of what makes its contribution useful in the first place.

“The power doesn’t start with the AI. It starts with what we bring to it.”

Download this Perspective
PDF · designed for reading, saving or sharing

Download PDF

There is a complication I have to take seriously, because it cuts against me. The 2025 Quarterly Journal of Economics study Generative AI at Work followed 5,172 customer-support agents and found the strongest gains among the less experienced and lower-skilled. AI helped them adopt some of what the stronger performers already did.

Nobody in that study had to define the problem from scratch. The work was defined, the workflow was known, and the tool was dropped into it. It worked. So the honest version of my argument is narrower than the slogan: where the problem is already well framed and quality is already well defined, you can add AI to an existing process and create real value. That is not a minor exception. It is one of the clearest ways organisations can benefit from AI.

But the study doesn’t show AI giving someone the judgement to decide what good looks like in an unfamiliar situation. That distinction matters more as the work becomes less defined.It can take you remarkably far into unfamiliar territory without giving you the judgement required to recognise the cliff at the end of the path.

The jagged technological frontier research makes the point from another direction. In the study, 758 BCG consultants became substantially faster and better with GPT-4 on tasks inside the model’s capability frontier, while reliance on it hurt performance on a task outside it. The skill isn’t simply knowing how to use AI. It is increasingly knowing where, how and how far to trust it. And that is a judgement about the work, not merely about the tool.

“

AI can make you capable of doing the work without making you qualified to judge it.

I see organisations making much the same mistake at scale. The seductive route is familiar: buy the tools, roll out Copilot, give everyone access, find a hundred use cases, run prompt training, add an agent here and a chatbot there, total up the hours saved and announce that the organisation is becoming AI-enabled.

None of that is wrong. But it can leave one rather important question unasked: should the process we’re accelerating still exist in this form at all?

Adding AI to a process can improve it. It can also help an outdated process produce its outdated result faster.

“AI is a terrible reason to put a turbocharger on a process that no longer deserves an engine.”

McKinsey’s State of AI in 2026 found that organisations reporting the greatest value from AI were far more likely to be fundamentally redesigning workflows rather than simply adding AI to existing ones. That doesn’t establish causality, but it is consistent with the distinction between AI adoption and AI transformation.

There is, however, a stronger objection to my argument. Sometimes you cannot know what genuinely better looks like until you’ve played with the technology. Nobody sat down and specified all the things a spreadsheet should eventually be used for before building one. Search, version control and countless other technologies found important uses because people first got access to a new capability and started messing around with it. AI is no different. People discover possibilities by using it.

So start with the outcome can become bad advice if it means don’t explore until you already know what you’re looking for. I don’t think those positions actually conflict. Exploration should be capability-led. Give people the tools, let them experiment, try things whose value you cannot yet predict and see what becomes possible.

But exploration and commitment are different activities. The mistake comes when nobody goes back and asks the outcome question before turning an experiment into a workflow, an agent, a platform, a headcount decision or a budget line. A promising experiment gets hardened into a permanent process before anyone checks whether that process deserves to exist.

“Explore from the capability. Commit from the outcome.”

Even exploration depends on something human. Somebody still has to recognise that what they have stumbled onto is interesting, useful or dangerous. Judgement has not disappeared. It has simply entered earlier in the process.

Once we move from exploration to actually changing how work gets done, I would stop beginning with Where can we use AI? I would begin with What are we trying to accomplish? For whom? Why does it matter? What would genuinely better look like?

Then comes the question of what the work requires. Where is human judgement essential? Where do context, empathy, expertise or accountability decide the outcome? Where can AI contribute speed, scale, synthesis or pattern recognition? What combination produces something better than either could produce alone?

Only then does it make sense to ask what the workflow should become — and what technology belongs in it.

It sounds obvious. Yet a great deal of AI adoption still runs the other way: technology, use cases, workflow and eventually, sometimes, purpose. That is how an organisation can become extremely proficient at using AI without becoming noticeably better at creating value with it.

And this gets more important as the technology improves, not less. Access will stop being what distinguishes anyone. The models will get better. The tools will spread. Today’s remarkable capability becomes tomorrow’s ordinary infrastructure.

What stays scarce is everything around it: the problems you choose, the questions you ask, the context you hold, the standards you set, the judgement you apply and the responsibility you take for the result.

I still believe in AI-empowered professionals. AI will make good professionals dramatically more capable, and it will let less experienced people do things they couldn’t do before. That’s the effect. Human-empowered AI is where the story starts.

We didn’t get the destination wrong. We got the arrow backwards.

Download this Perspective
PDF · designed for reading, saving or sharing

Download PDF

All Perspectives › 100% Written by Me. 100% Written With AI.

I use AI when I create content. By default, actually. And, increasingly, happily and with full conviction.

Even as I see that sentence materialize on my screen, I feel a faint urge to defend myself. Yes, I use AI, but the ideas are mine. Yes, it helps me write, but I rewrite. Yes, I use ChatGPT, but I could write before generative AI existed. Somewhere along the way I started to wonder why I was behaving as though I’d been caught.

Back at school, writing came easily. I generally earned top marks for creative writing; I wrote lyrics for our band and discovered the small thrill of other people responding to words I had written; and even when our language teacher terrified the class with modern poetry, I was happy to have a go. Perhaps the shameless confidence of adolescence simply let me go down the slippery slope of writing without ever touching the handbrake.

Then business writing came along, where words committed to paper could later be quoted back at you. As long as it had a clear job to do, I could still produce presentations, proposals and internal arguments without much hesitation. But ask me to write a public piece that simply said, “this is what I think and this is why,” and the machinery changed. Every sentence looked permanent, every claim wanted another qualification, and every paragraph seemed to apply for planning permission before I could build the next one.

I tried the recommended remedies. Ann Handley’s TUFD told me to get the rough thing down before making it good. John Steinbeck’s second rule urges us to write freely and rapidly, then repair later. Stephen King distinguishes between writing with the door closed and rewriting with the door open. All three, in different ways, reveal one of the keys to better writing: allowing the bad draft to exist before asking it to be good. And that was exactly my problem. Even the rough draft felt like an MVP, and in my head the V mattered far more than the M. It had to feel viable before I let it exist. Once my words started hitting Word, the handbrake came back on.

Download this Perspective
PDF · designed for reading, saving or sharing


Download PDF

My first, almost successful, workaround came years before AI. I started dictating, because speaking had never suffered from the same problem. Give me a stage and an idea I understand, and language tends to follow the thought. Connections appear, arguments move around, and sometimes a phrase leaves my mouth in better shape than I knew it had been in my head.

Dictation got me moving, but it rarely got me all the way to Draft One. Somewhere mid-draft, the handbrake came back on: I started repairing sentences before I had finished drafting the thought.

Then AI entered, and it did something dictation alone couldn’t: it helped me keep moving long enough to reach Draft One. It did not remove the doubt; it moved it later in the process. The exchange was fast and fluid enough for me to stay with the thought instead of stopping to repair every sentence as I went. In effect, AI finally helped me do what Ann Handley, Steinbeck and King had all been pointing towards: let the imperfect draft exist before trying to make it good.

“It did not remove the doubt; it moved it later in the process.”

My process is not throwing rough ingredients into a machine and waiting for polished prose. I may start with a dictated argument, a few paragraphs I wrote, or an idea I can see clearly in its unfinished shape. I ask what argument AI hears, where the logic jumps, or what I am assuming without saying. Sometimes it finds the missing link. Sometimes it confidently finds the wrong one, which can be just as useful because explaining why forces me to become clearer.

From there we work back and forth. I add context, it proposes a structure, I reject it, it questions a distinction I think matters, I explain why, it offers alternatives, and I dislike most of them. By now, AI and I are almost like an old couple: we disagree wholeheartedly on a regular basis. Somewhere in that mildly argumentative exchange, the thought usually gets better.

Sometimes it hands me back my own thought with the hedging removed. Sometimes I reject what it gives me entirely. Either way, the conversation keeps me moving. After more experimentation than I care to count, I have landed on a conclusion that still feels odd: AI is the best writing partner I have ever had.

“

AI and I are almost like an old couple: we disagree wholeheartedly on a regular basis.

That does not make it the author. If I ask it to manufacture expertise I do not have, invent experiences I never had or formulate opinions I never bothered to form, something has gone badly wrong. The problem is not that AI touches the work. The problem would begin if I disappeared from it.

“The problem is not that AI touches the work. The problem would begin if I disappeared from it.”

AI slop is real. But let’s be honest: human slop existed long before ChatGPT. AI did not invent mediocre content, it just made mediocre content nearly frictionless to produce. So the opposite of AI slop is not necessarily human-only content. What interests me more is human-empowered AI. I bring experience, judgement, curiosity, taste, questions and stubbornness. The machine brings capabilities I lack. Sometimes the combination beats what either generic AI or my old solo process would have produced.

And if my name is on the result, I remain responsible for it. We spend a lot of energy policing who used AI, how much, and whether they should confess to it. But when the question is whether the resulting content deserves anyone’s attention, I think we may be asking the wrong question. We keep questioning the writer about the purity of the process, while the reader has a much simpler encounter: is this worth my attention?

Readers do not calculate the purity of your production process. They stop, scroll past, question, disagree, share, remember, or carry a thought somewhere unexpected. Sometimes the point I considered central barely registers, while a small observation halfway through starts the conversation. That is useful, not because I want to optimise every sentence for clicks, but because listening tells me what stayed unclear and what mattered to readers that I had underestimated.

“Readers do not calculate the purity of your production process.”

Which, I suppose, is my actual confession, if I still need one. I sat down thinking I had to admit that I use AI. Having written it out, I’m mostly left wondering why I thought it needed admitting at all. The partnership gets better as I get better at directing it, resisting it and listening to readers. Dictation taught me how to release the handbrake. AI helped me stay with the thought once I started moving.

And if you still want a percentage, this is the only one I can honestly give you:

100% written by me. 100% written with AI.

With my name attached, so you know exactly where to send your agreement, disagreement, questions or objections.

Download this Perspective
PDF · designed for reading, saving or sharing


Download PDF

All Perspectives › Prompting Is New. Briefing Isn’t.

Imagine briefing Michelangelo for the Sistine Chapel.

At one extreme, you could say: Please paint the ceiling. Plenty of freedom, not much help. At the other, you could specify the colours, scenes, figures and positions, perhaps ask for three sketches by Thursday. Plenty of instruction, not much Michelangelo.

Many years ago I came across a presentation built around exactly that thought. Damian O’Malley imagined what the brief for Michelangelo’s Sistine Chapel ceiling might have looked like, and Steven Stark turned the idea into a slide deck.

The cleverness was in what happened between those two extremes. A good brief could be clear about the ambition and meaning of the work while leaving the artist enough room to do something the commissioner could not have designed himself.

I have thought about that presentation surprisingly often over the years, partly because marketing has spent roughly the same period complaining about briefs.

Agency people complained that clients could not write them. Clients complained that agencies did not follow them. Creatives complained they were either vague enough to mean anything or detailed enough to make creativity unnecessary. And almost everyone has at some point received some version of: Make it innovative, but on brand. Be bold, but don’t frighten anyone. We want something disruptive. By Friday.

The remarkable thing is not that so many briefs were bad. The remarkable thing is how much good work still came out of them.

There was a reason for that: for years, great debriefing compensated for bad briefing.

A good strategist, creative, consultant or agency team rarely treated the written brief as holy scripture. They asked questions. They listened for the thing the client kept circling around without quite saying. They knew the organisation, the politics, the category and sometimes the client well enough to recognise that “we need a campaign” actually meant “we have no compelling reason for anyone to care about this product yet.”

They read between the lines. Occasionally they read between lines that weren’t even there.

In other words, capable humans became remarkably good at rescuing those who gave them mediocre instructions.

And then along came AI.

One of the more educational features of working with generative AI is its slightly irritating tendency to expose what you actually asked for rather than what you vaguely remember meaning. Ask a generic question and there is a decent chance you will receive a generic answer. Forget important context and the machine will not necessarily infer the particular piece of context that seemed blindingly obvious inside your own head. Give five conflicting ambitions and it may cheerfully attempt all five.

Then we look at the result and declare: AI is producing rubbish.

Sometimes it is. But sometimes a disappointing AI answer is less a failure of the model than an X-ray of the brief.

“Sometimes a disappointing AI answer is less a failure of the model than an X-ray of the brief.”

That is one reason I am increasingly sceptical about treating “prompt engineering” as an exotic new discipline built around secret incantations. Of course there are techniques worth learning, and the technology has its peculiarities. But much of what makes an AI instruction better is remarkably familiar.

What are we actually trying to achieve? For whom? In what context? What is already known? What matters most? What constraints are real? What should not happen? What does good look like? And where do I want the recipient to follow my instructions versus use judgement of its own?

Prompting may be new. Briefing isn’t.

Download this Perspective
PDF · designed for reading, saving or sharing


Download PDF

Perhaps the most important part is the last one, because a good brief is not an instruction manual.

If I already know precisely what the answer should be, I don’t need much intelligence on the receiving end. I need execution. The reason we brief talented humans, and increasingly capable machines, is precisely because we expect something from them that we did not completely specify in advance.

That creates the tension at the heart of good briefing.

Too little direction and we create drift. Too much and we create obedience.

Freedom without direction creates drift. Direction without freedom creates obedience. Good briefing creates room for judgement.

“Freedom without direction creates drift. Direction without freedom creates obedience. Good briefing creates room for judgement.”

Somewhere while getting better at giving instructions to AI, I realised that this was no longer just a marketing lesson. Briefing and managing share a surprisingly difficult task: defining intent and boundaries without defining the answer.

Good managers do not simply throw an objective over the wall and call that empowerment. Nor do they specify every move and then wonder why nobody shows initiative. They establish what matters, what is fixed, where the risks lie, what success means and where another person is expected to think.

In other words: clear intent, scoped instructions and defined freedom.

The point is not that managing humans is the same as prompting machines. It very obviously isn’t. Humans bring relationships, emotions, tacit knowledge, ambitions, insecurities, institutional memory, dissent and the occasional desire to spend the afternoon doing something entirely different. Long may they continue to do so.

The more interesting lesson runs in the opposite direction.

AI is not teaching us to manage people like machines. It is exposing how casually we have sometimes given direction to people.

A strong colleague can quietly compensate for a weak manager. They ask the question that should have been answered before the assignment began. They resolve contradictions. They infer priorities. They know that when the boss says “quick first draft,” it may somehow still need to be board-ready.

Their rescue can hide just how poor the original direction was.

“

AI is not teaching us to manage people like machines. It is exposing how casually we have sometimes given direction to people.

Good people have always been remarkably good at protecting managers from their own bad instructions. AI is less discreet.

That may turn out to be useful. AI gives us something close to a high-speed practice environment for delegation. You give direction. You see the result seconds later. You notice what was missing. You clarify the objective. You remove an unnecessary constraint. You explain what you meant by “more strategic,” because apparently that phrase was not quite the masterclass in precision you had imagined. Then you try again.

A feedback loop that might take days in an organisation can happen repeatedly in minutes.

We thought AI would mainly accelerate production. It may also be accelerating our education in giving direction.

“We thought AI would mainly accelerate production. It may also be accelerating our education in giving direction.”

And that lesson is likely to outlast today’s prompt techniques. Models will change. Interfaces will change. Many clever prompting tricks will disappear into the products themselves.

Being able to formulate intent, establish context, make choices, articulate constraints and leave useful room for judgement will not.

If anything, that becomes more important as the intelligence available to us increases. The better the person on the receiving end of a brief, the less sense it makes to prescribe everything they should do. As AI becomes more capable, the same principle starts to apply there too.

Capability raises the potential value of freedom, but only when freedom has meaningful direction.

Which takes me back to Michelangelo.

The point of that old Sistine Chapel briefing story was never that the commissioner should simply have said: You’re Michelangelo. Surprise me. That would not have been a great brief either.

The magic lies somewhere between control and abdication: enough clarity about purpose to point the work somewhere meaningful, enough boundaries to make the problem real, and enough freedom for somebody else’s intelligence to contribute something you could not have specified yourself.

For decades we relied on good people to repair bad briefs downstream. AI is pushing more of that responsibility back upstream, towards the person giving the instruction. That feels like progress.

And it suggests a simple test before you brief a colleague, agency or AI.

Can you answer four questions clearly: What are we trying to achieve, and for whom? What is fixed, and what is genuinely open? What does good look like? And where do I want execution versus judgement?

If you cannot answer those, another clever prompt probably will not save you.

If you can, resist the temptation to specify the rest.

The better the intelligence on the receiving end, the less useful it is to specify the answer. Our job is to specify the intent.

Download this Perspective
PDF · designed for reading, saving or sharing


Download PDF

All Perspectives
›
If Content Costs Nothing to Make, Why Exclude Anything?

There used to be a moment in every content plan when somebody said we don’t have the capacity for that.

It was never a strategic moment. Nobody stood up and invoked Porter. Somebody looked at four people, a budget and a six-week turnaround, and the idea died of arithmetic. But that was the moment the strategy got made. Capacity did the choosing, and the document took the credit.

That moment is gone. The eleventh theme now costs a decent brief and an afternoon. The extra channel costs a repurposing step. The stakeholder request that would once have been quietly starved of resources can be honoured by Thursday.

Nothing in the system says no on your behalf any more. Exclusion used to be automatic. It is now entirely voluntary, and voluntary things tend not to happen.

What did we actually decide?

I have read a lot of content strategies. They are usually well made: audiences defined, themes set, channels mapped, formats selected, KPIs attached, everything landing neatly in an editorial calendar. Nothing is wrong with them, and that is what I have started to find suspicious.

Because when everything has found a place somewhere, I am left with one question the document never answers. Not what did we organise. What did we choose at the expense of something else?

Which audience matters more when two audiences want different things. Which channel are we deliberately not going to invest in. Which perfectly sensible request does this document give us permission to decline.

“If nothing was refused, this is not a strategy. It is a very well organised list of things we would quite like to do.”

Download this Perspective
PDF · designed for reading, saving or sharing


Download PDF

Not long ago I helped a team present a repositioning to its internal decision makers. We brought three slides. The first showed the direction we had chosen. The second showed the directions we had considered and rejected. The third described what the new direction would mean in practice: for activities, for priorities, for the results people should expect.

The longest discussion of the session was about the second slide.

Several people were not sure why it was there at all. Others tried to soften it. Surely these were things we would do later, or things of lower priority. Not felt like a strong word for options that still looked perfectly good on paper.

It took a long explanation before a majority saw the point. And when they did, something useful happened. They understood the chosen direction better than they had from the slide that described it. The trade-offs made the choice legible in a way the choice could not make itself.

I have been calling it the NOT-slide for years, and the name has never mattered more than it does now. What surprises me is that I still have to argue for it. I would expect it to be standard procedure, the way a risk register is standard procedure. Clarity about what you are walking past is not a rhetorical flourish. It is how everyone else in the building knows what the direction actually costs.

“

The trade-offs made the choice legible in a way the choice could not make itself.

At which point a reasonable CMO asks: if content costs nothing to make, why exclude anything?

It is a fair question, and it is the one that makes this an argument about 2026 rather than a restatement of something Michael Porter settled in 1996. If content were still expensive, focus would be a budget conversation. It isn’t, so it has become something else.

Two things stayed expensive when production got cheap.

The first is attention, and not only the audience’s. Every theme you add is a claim on the same finite quantity of internal attention: the review cycles, the subject-matter experts, the arguing about tone, the maintenance. A marginal piece is cheap to make and just as expensive to make matter as it ever was.

The second is harder to see and matters more. Your content is no longer read only by readers. It is read in aggregate by systems that summarise you to people who will never visit your site. Those systems do not sample your best work. They describe the shape of the whole thing.

“The eleventh theme does not sit harmlessly at the bottom of the site. It votes.”

Which means the eleventh theme does not sit harmlessly at the bottom of the site. It votes. A body of work with nine interests gets summarised as a company with nine interests, which is another way of saying no position at all. Everything you couldn’t say no to is in that summary.

Why content teams find this so difficult

Because most of them operate, partly, as internal service organisations. People arrive with requests, and good teams want to help. Can you make something around this. Could we support that launch. Shouldn’t we be doing more video.

Every one of those requests is defensible on its own. That is precisely the mechanism. Over time, helpfulness compounds into accumulation, and the strategy quietly becomes an accommodation device in which everyone can find themselves somewhere.

There is a second trap, and it runs the opposite way. Content teams worry about repeating themselves because they have lived with an idea internally for months. An idea can feel old internally long before it has become familiar externally. So teams subtract for the wrong reason, boredom, and add for the wrong reason, novelty, while the thing that was starting to compound gets quietly retired in favour of something fresh.

“An idea can feel old internally long before it has become familiar externally.”

Two things that work on any Tuesday

One. Ask whether the work needed us at all.

In earlier work I have separated the thinking behind a piece from the wording of it, and used a counterfactual test for authorship: would this have existed without you? It works just as well pointed at a content plan. If a competent model with a good brief would have produced substantially the same thing, it does not earn a slot, however useful it looks.

The sharper version separates the two questions. Is the thinking ours, or only the wording? Work where only the wording is ours is exactly the work that fits effortlessly, costs nothing to approve, and adds nothing to the shape of the whole. It fits because it is generic. That is the reason to drop it, not the reason to keep it.

Two. Make subtraction a name, not a sentiment.

Give the strategy a NOT-slide. The audiences, channels and themes you are leaving to others this year, on one page, in the same deck as the direction. Then enforce one rule: no addition is approved without naming, in that document, the specific activity that now gets less. Not “we’ll find the time.” The name of the thing.

And watch the room for the word later. It is the polite form of not, and it is how a NOT-slide quietly turns back into a backlog. An option parked as later keeps its claim on attention while giving nothing up, which is the whole problem wearing a calendar entry.

The point of writing it down is not tidiness. It is that you can point at a page when you decline a colleague, instead of reopening the entire strategy every time someone arrives with a reasonable idea.

And once a quarter, review the calendar backwards. Most teams ask what should be added. Ask what should come out, and then ask the harder version: what should come down. If your published corpus is now the evidence from which you get described, a deletion project is a strategic act, not housekeeping.

The question I would put on the first page

Focus is not making less. It is making more of what matters and less of what merely fits. The difference only becomes visible when something reasonable gets refused.

So before the audiences, the themes and the channel matrix, I would put one question at the front of the next content strategy I read:

What deserves three years of our attention rather than three weeks?

Everything that cannot survive that question is still on your site. Quietly helping a machine explain you as an organisation with a great many interests and no particular position.

The NOT-slide for this piece: measurement, AI tooling, and whether you should publish less. Three other essays. Not this one.

Download this Perspective
PDF · designed for reading, saving or sharing


Download PDF