We have hundreds of articles sitting ready to publish across our media portfolio. They’re not waiting on the AI. They’re waiting on us. The slow part of our operation isn’t drafting any more, it’s the human work around it, and that turn is what most publishers I talk to haven’t fully clocked. I call it the bottleneck shift: when AI accelerates one stage of a workflow, the humans around it usually become the next thing in the way.
I run mOOnshot digital from inside that shift. Our content pipelines produce drafts faster than our team can review and publish them. The queue isn’t short of quality articles. It’s short of reviewers’ and designers’ time.
Why is AI no longer the slow part of the publishing pipeline?
Because drafting used to dominate the calendar, and that’s the stage AI has absorbed. Once that stage accelerates, the next-slowest one becomes the new ceiling. The stages that sat upstream and downstream of writing turn out to be where most of the work actually lives.
Two years ago, producing a well-researched, on-brand 1,500-word article meant scoping, briefing, drafting, and editorial passes over several days of a writer’s time. Today our pipeline produces a publication-grade 1,500-word article in the voice of the title it’s destined for, at a cost that would have been impossible to model before we rebuilt around AI operations.
It took time and careful fine-tuning to land the quality where we want it. Our AI agents work from a detailed internal content framework we’ve custom-built for each of our publications, drawing on years of editorial work, with brand voice, structural rules, and quality gates specific to each title.
I walk through that process in more detail in a separate piece on how I replaced a 15-person writing team with AI agents.
The result isn’t that work speeds up evenly across the workflow. Once writing accelerates from days to minutes, the stages no one was paying much attention to suddenly become the ones you stare at every morning.
Where does the human side actually slow the pipeline post-AI?
Keeping humans in the loop slows the workflow down in three places, and each of them gets less attention than it deserves.
Visual production
A published article needs custom images: a custom cover image, in-body photos, social cards, occasionally a diagram or an infographic. Generic AI-generated images don’t meet our quality standards. We often still use our own photos and a human always has to make the final call on what goes on the page.
Our product reviews go further still. For many of them, we run a proper photoshoot: organising the setup, sourcing and staging the product, taking the photos, then selecting and processing the best shots into the story. That workflow does not accelerate with AI. It is a stage in our workflow that sits between an AI-ready draft and a publishable article. When you think of the visual stage as “generate a hero image”, it sounds easy and quick. When you actually implement it as “plan, shoot, edit, and land a full visual story per review”, the visual step takes real time no matter how fast the drafting is.
The visual team is now the slowest part of our publishing workflow, not the writing team. Every article sitting in our ready-to-publish queue is waiting on a visual decision that a human still has to make. The pipeline can generate options, but choosing between them and organising actual photoshoots still take human time.
Brand-safety and editorial review
At our scale, every piece still goes through a mandatory human-in-the-loop review before it gets published. Not because the AI drafts are bad. Because the risk of publishing a single brand-damaging article across our portfolio is larger than the cost of the review.
We learned this the hard way early on. I asked Claude Code to clean up partner links across one of our WordPress databases. It ran for two days. The first day’s changes looked clean. The second day’s did too. Then a few days later the broken-link reports started showing up in our analytics. The agent had decided, halfway through, that a search-and-replace on brand names would speed things up, without checking that those names also lived inside longer, perfectly valid URLs. Confident, precise, completely wrong. Backups saved us, but the lesson stuck: human review on anything touching live data is not optional.
Human review gates matter most where the risk is widest. Once you’ve been through that, you stop treating review as overhead and start treating it as necessary.
The cognitive load of approving content you didn’t write
This one surprised us. Reviewing a 1,500-word AI draft, even a good one, is genuinely tiring in a way that reviewing a draft from a writer you’ve worked with for years isn’t. Our reviewers are reading more carefully because they cannot yet trust the AI agents’ output, regardless of how confident they sound. The result is that humans can’t review new content fast enough to match the AI pipeline generation speed.
Review time is also calibration time. Every round of edits is feedback the editor sends back into the pipeline so the next draft gets a little better. That’s slower in the first few cycles and faster after that. We’re already seeing it inside our publications: each new article is getting quicker to review and approve as the system learns what “on-brand” looks like for that specific title.
We’ve also added an editor agent that reviews the writer agent’s draft before anything reaches our human editor-in-chief. So the human is the final reviewer in the chain, not the first. That alone has cut review time noticeably, and it’s the bottleneck shift at work in miniature: once the first review is AI, the new slow stage is calibrating the editor agent, not editing the drafts.
Accelerating the human side: what worked for us
While the challenges explained above are slowing down the publishing schedule, we’ve identified three solutions that help speed things up: batched reviews, templated visual systems, and upstream quality gates. We have not solved the human-time bottleneck. But these are the bets that are paying back.
Batched reviews
One reviewer in a focused two-hour block moves faster per article than the same reviewer doing one article at a time across a week. Our experience is that batched reviews also produce more consistent judgement across the batch. Feedback is then incorporated into the next batch of articles to further improve the output quality.
Templated visual systems
This is how most scaled publications have always worked, but AI makes it non-optional. A clear hero-image system, with ratios, palette, typographic overlays, and prompt templates specified once, means the visual decision on any given article is much easier and faster. It also means that it can often run in parallel to the writing pipeline. Our designer doesn’t have to wait for the final copy to be approved to start producing visuals.
Upstream quality gates
Most of what we used to catch in editorial review was actually a brief-quality issue: unclear angle, missing audience context, weak thesis. AI drafts inherit those upstream failures at high speed. Tightening the brief, and the context passed into the drafter, is cheaper than fixing the output, and it makes reviewer time go significantly further.
None of these three remove human judgement from the loop. They reshape the loop so we spend our time on the things that actually need a human, and let the pipeline handle the parts it can.
Three levers, one reshaped loop
Each shifts human time to the things that actually need a human, and lets the pipeline handle the rest.
- Batched reviews
Two focused hours per reviewer beats one article a day across a week. Judgement is more consistent across the batch, and feedback loops back into the next pipeline run.
- Templated visual systems
Ratios, palette, overlays, and prompt templates specified once. The visual decision per article shrinks, and production runs in parallel to drafting.
- Upstream quality gates
Most editorial fixes are upstream brief failures travelling at AI speed. Tightening the brief is cheaper than fixing output and stretches reviewer time further.
What does the bottleneck shift mean for organisations beyond publishing?
Every team deploying AI internally runs into a version of this. Customer support automates first-draft responses and the queue moves to escalation review. Marketing automates content production and finds the new wait sitting with legal and stakeholder sign-off. Engineering teams I talk to are running into it on the review side: AI writes the code faster than anyone can read it. The pattern holds wherever a human-in-the-loop gate sits downstream of an AI-generated output.
Most operators I talk to are still treating the AI investment itself as the transformation. It isn’t. The AI investment is the trigger. The transformation is whatever the organisation does once it realises the new ceiling is somewhere else entirely, and it’s almost always a place the existing org chart wasn’t designed to scale. For media companies specifically, I’ve made this argument in Most Media Publishers are solving the wrong AI problem.
The honest question for any team running AI in production is the one we keep coming back to at mOOnshot digital: where does the work actually stop today, and what would accelerate the new slow stage? The answer is almost never AI itself.
The AI transformation isn’t done when AI can write
What comes next, once AI writes faster than humans can review, is rebuilding the human workflow around everything AI has changed. That’s the harder part.
Naming the shift is the easy part. The work is rebuilding the human side around it, and most teams haven’t started. That’s what AI-native publishing really means: a pipeline built around agents from the start, paired with a human workflow rebuilt for the new constraint.
The discipline I use to structure that rebuild is in Zero-Base Operations.
I publish these essays to spark new conversations. If this one resonated, or if you have questions or pushback, reach out via LinkedIn, X, or hello@simonbeauloye.com.
Cited byPerplexity11Gemini5ChatGPT4Google AI3
Spotted something I got wrong? hello@simonbeauloye.com
