writing — 02
The productive mess.
by Bob · · a 5-minute read · the pain of doing it yourself
The first month of AI content feels like a miracle. Marketing ships three times the posts. Sales builds its own decks and stops asking. Customer success writes its own one-pagers. Product documents itself. Everything arrives fast, everything looks good, and everyone gets praised. I believe this is exactly what's happening inside most organizations right now — and that almost nobody has looked under the hood at what's actually being produced.
fig. 01 — everyone shipping, nothing connected: fast, in five directions. The red outputs are the ones that contradict the yellow ones. Nobody's checking.
It feels like productivity. It compounds like debt.
Look under the hood at month six. There are five descriptions of the same product in circulation, each subtly different. Three visual dialects, because every team's AI learned from a different pile of old decks. A capability that's still in beta being sold as generally available in one deck and hedged in another. Tone that swings from enterprise-solemn to startup-chirpy depending on which team shipped the page. Nobody is wrong. Everybody is fast. And the whole is less coherent every single week.
The cruel part is that it registers as winning. Output is up and output is measurable; drift is invisible and nobody owns measuring it. So the mess grows inside the good news.
Why this happens — the constraint that quietly mattered
AI removed the production constraint. It did not remove the coordination constraint — it stressed it. Here's the part almost nobody notices: coordination used to happen by accident, inside the bottleneck. When one writer, one designer, and one review queue produced everything, consistency wasn't a discipline — it was a side effect of scarcity. The same few hands touched every asset, so every asset roughly agreed.
Remove the bottleneck without replacing its hidden function and you get exactly what the diagram shows: loops without a core. Every team spinning beautifully. Connected to nothing. Correcting toward nothing.
And it's worse than it used to be, because the audience changed. Machines read your output now. Search engines and AI engines cross-reference every page, and when your own assets contradict each other, the contradiction is machine-readable. You're not just confusing a prospect who might forgive you — you're teaching the engines that your company is an unreliable source about itself.
The under-the-hood test
Ten minutes, genuinely uncomfortable: pull the last ten assets your organization shipped — any team, any format. Lay them side by side and ask four questions. Do they describe the same product? Do they use the same names for the same things? Do they make the same claims about what's available today? Can anyone say where each claim came from? Most organizations fail on names alone — before you even reach the claims.
What doesn't fix it
The reflex is governance theater: a brand police, a fifty-page style PDF, an approval board. All three reintroduce the bottleneck — you pay for AI speed and then queue it behind a human meeting, which is the worst of both worlds. The style guide is unread by the people and unreadable by the machines. The review board becomes the thing everyone routes around, quietly, with the best intentions.
What fixes it — give the loops a core
The speed was never the problem. The problem is that every loop is generating from its own memory of the product. So give them one memory: a living map of what you sell — every item, every team's definition, every lifecycle phase, versioned as it moves. Make the assets reference the map by construction, not by policy: the deck pulls the node, the page pulls the node, the post pulls the node — so they can't disagree, because they're quoting the same source. Put gates at the seams instead of gatekeepers in the middle: machine checks plus a human sign-off where it counts, so nothing ships wrong but nothing waits on a committee. And let every asset register back where it lives, so when the truth changes, everything that tells it queues for the update.
fig. 02 — the fix isn't slowing the loops down. It's giving them something to agree with.
The uncomfortable summary
Fast is table stakes now — everyone is fast, or will be by next quarter. Coherent is the differentiator, because coherence is what buyers feel and what machines cite. The mess is not a phase that passes; it compounds until someone gives the loops a core. The good news: the core is buildable, it's smaller than it sounds, and the speed you fell in love with survives it. The mess is optional.
look under your hood
Statement 06 on the litmus is the ten-minute version of this essay. The full argument for the core is one living map of what you sell — and the way out is shorter than the mess suggests.