Writing was never the bottleneck

Last issue I argued that not every story deserves the same investment, and that the first editorial decision is acting on that. Say you have. You have a story worth telling and you have a great interview.

The draft is finished on day two.
The story publishes in week nine.

Everything in that gap is the actual job.

It was never a writing problem. It was a consent problem, wrapped in a coordination problem, running against a clock.

The advocate is never more willing than the day they were interviewed; everything after that is decay.

AI creates drafts ten times faster, yet time-to-publish hardly moved. Ask anyone running a program how long a story takes from interview to published page and the answer is still measured in weeks: six to twelve of them.

So where did those three days go? Nowhere useful. Three days out of sixty. Writing was never the bottleneck.

01  The only content that needs someone else's permission

We all know the team members (mentioning no names, brand) who conveniently forget a customer story is the only marketing asset that cannot exist without the agreement of an organisation that does not work for you.

In my agency life my pitch was this: "You give us budget, and we may or may not be able to create something, at some undetermined point in the future, and when you have it you may or may not be able to use it."

Compelling value prop; right!?

Advocates did not choose your deadline, they carry all of the risk if it goes wrong, and they get almost nothing out of it.

Their legal team has never met you. Their comms team has its own calendar. Their executives have a reputation attached to every number in your draft.

With 'proper' programs the advocate owns the words in perpetuity; their control over how those words are used does not expire when you publish, and they get real value from taking part.

02  What actually eats the weeks

None of it is mysterious; it's just rocks on your runway, which is why the weak give up and customer advocacy pros rule!

The internal review. Product marketing wants a feature described differently. Someone senior wants the numbers to lead. A fifth reviewer disagrees with the first four, and no-one sees their colleagues' comments.

The advocate's own chain. Your advocate is enthusiastic; their legal team is not. Their comms team even less so. Sign-off on a quote and a logo can take a day, or it can take two months, and you don't find out which until you are in the thick of it.

Version chaos. Three drafts circulating as email attachments. Someone edits the wrong one, changes are lost, and noticed a fortnight later.

The chase. The biggest user of time and the one that's glossed over in every process diagram. Following up. Waiting. Following up again. Being polite about it. This is an area where automation might actually make things worse.

Stakeholder churn. By week eight, the person who commissioned the story has changed role. The new person has questions.

03  The half-life of a yes

Six to twelve weeks. One in five never publish.

These two numbers aren't separate facts; they're the same thing. The weeks are how the story dies.

You win an advocate's consent on the day you interview them: the result is fresh, they are proud of it, they like you, and they have just spent forty minutes telling you why it mattered. Peak enthusiasm.

But consent now isn't the same as final story approval weeks later: sign-off on the exact words, the number, the quote, the logo, from the advocate and perhaps legal and comms. You win consent at the peak. You need approval at the trough.

And enthusiasm is perishable. By week three the result no longer feels fresh. By week six it has cooled into obligation. By week eight, answering your emails is a favour they are doing you. Nobody says no; approval just slides down the list until one in five never publish at all. The other four publish, but rarely as the story you started with and often the poorer for it.

Ten times faster drafting with AI, on a process where drafting was three days out of sixty. That's not a productivity gain; it's a rounding error.

Speed matters, but not for the reasons often mentioned. It matters because momentum is the only thing that carries day-one enthusiasm to a day-sixty approval. A story that moves keeps its yes. A story that stalls loses it, quietly, and turns up six months later in a spreadsheet marked "dead".

04  Herding cats

Take the drafting to almost nothing and what remains is the coordination: two organisations, five to ten people, at least one department that has never met you, and a shared understanding of the truth that has to survive all of them, before the willingness at the centre of it runs out. It accounts for almost all of the elapsed time and none of the perceived value.

05  What actually moves the needle

Here are things that genuinely help. None of them involves AI. Every one of them is about protecting consent, or protecting momentum, or both.

Get the approval commitment at the beginning. When the advocate says yes to the interview, that is the moment to ask who signs off, how long they take, and whether legal/brand need to see it. Not in week six, when you discover their PR team. Ask while enthusiasm is at its peak.

One living document, not an email chain. Every version circulating as an attachment is a future disaster. A single source of truth with comments on it removes an entire category of delay; it also ends the argument about which draft is current.

Publish the internal review timeline (and stick to it). Seven to ten working days for most stories; longer if legal is involved. Silence after the deadline means approval, and everybody agreed to that before the clock started.

Send the advocate the draft before their legal team sees it. They will fight for the story internally in a way you never could. Give them something they are proud of first, while they still care.

Reduce the number of approvers. The hard one; political rather than procedural. Every additional approver adds their time and coordination overhead; the cost compounds. Most stories carry at least one reviewer who is there because of an org chart rather than a need.

Set roles and responsibilities. Everyone's a storyteller, or so they think. Product marketing comments on technical specifics, not the prose.

06  Why nobody fixes it

Nobody was ever promoted for shortening an approval cycle.

Fixing coordination has no launch moment. You cannot put "we reduced our average legal turnaround by eleven days" on a slide and expect applause, even though it's worth more to the program than any tool. The work is unglamorous, cross-functional, and involves asking senior people to give up a review they enjoy having.

The Citizen Editors of Issue 001 are not just editing prose. They are the ones holding the consent together; chasing, translating, reassuring, deciding what can be conceded and what must be defended, keeping a yes alive long enough to publish it. That is the skilled work now. It always was. We just used to call it admin.

07  What comes next

This is the third issue of Proof Positive. We have established that everyone is now an editor; that not every story deserves the same investment; and that the time was never going where we thought.

Next issue: the interview is everything. If the draft now writes itself from whatever material you feed it, then the quality of that material is the whole game. And the interview is not only where the story is found; it is where the consent is won. Subscribe if you have not. Forward to one person currently waiting on a legal team.

§

Robin Hamilton is the founder of Proofpoints, the customer storytelling platform launching in 2026. Previously, cofounder and CEO of inEvidence. Proof Positive is published fortnightly.

Two weeks from now, in your inbox. Fortnightly, no spam, easy unsubscribe.