First, trace recent pieces from idea to publication
Pick the last handful of pieces that went live and rebuild each one's history from the calendar, the shared documents and the message threads. For every piece, note the date the idea was agreed, the date the brief was approved, the date the first draft arrived, each date it went to and came back from a reviewer, the number of full rewrites, and the publication date. Then split the elapsed time into two kinds: time someone was working on the piece and time it sat waiting. Most teams find that waiting dwarfs working, and that the waits cluster at one or two stages. The stage where work waits longest is the constraint in theory of constraints terms, and speeding up any other stage only adds to its queue. If the trace shows that drafting really is the constraint, the guide to working with freelance writers covers adding drafting capacity with a brief, a style guide and a review gate in place.
The pattern points at the cause. Long gaps between draft and approval with many comment rounds suggest review; drafts that came back as near-complete rewrites suggest the brief; weeks between idea and brief suggest the calendar; a flat line of activity on pieces nobody mentioned suggests the workflow itself is invisible. Record the elapsed days per stage as a production KPIA metric tied directly to an objective. so the effect of each fix can be read later. If the hold-up is a cross-team launch rather than the content line, the content marketing troubleshooting hub points to the other symptoms in this family.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| First drafts come back needing a full rewrite | Whether the brief named a question, reader, angle and proof before writing | Briefs too vague | Brief every piece before a writer starts |
| Drafts sit for days, then return with conflicting comments | Number of reviewers per piece and who can make the final call | Too many reviewers, no decision-maker | Name roles; one final approver per page type |
| Weekly meetings debate what to write next | Whether pillars and a sized calendar exist and are used | No pillars or calendar | Derive pillars; plan the month ahead |
| Every channel needs a fresh piece and the team never catches up | Share of output that is derived from existing assets | No repurposing | Build format ladders from proven sources |
| AI drafts are fast, but editing them takes longer than writing | Whether prompts carry the brief and sources, and what the review checks | Unclear AI review rules | Prompt from the brief; set a review gate with owners |
| Nobody can say where a given piece is or why it stopped | Whether stages, owners and due dates are visible in one place | No workflow stages | Define stages with owners and a shared board |
Fix, verify and prevent each cause
Briefs that leave the writer guessing
A brief that names a topic rather than a question lets the writer choose the reader, the angle and the depth, and the reviewer then judges the draft against a different picture. The rewrite that follows is the single largest hidden cost in most lines.
Fix: require a brief with the question, the reader and stage, the angle, the proof list, the outline and the review criteria before any writing starts, using the tutorial on writing a content brief; record the target query and its Search IntentThe goal behind a search query: to learn, to find a site, to compare or to act. for pieces meant to be found in search.
Verify: the share of first drafts accepted with edits rather than rewritten rises over the next month, and the draft-to-approval stage shortens.
Prevent: refuse to schedule a writing slot until the brief has been reviewed by the person who will judge the draft.
Review by committee
When every stakeholder may comment and nobody may decide, drafts wait for the slowest reader and then absorb contradictory changes.
Fix: assign the roles set out in the content governance guide, so that an editor owns structure and style, a subject reviewer checks only flagged claims, and a single approver signs off the page types that carry legal or brand weight; give each reviewer a turnaround agreed at the brief stage.
Verify: comment rounds per piece fall, and time spent in review drops while the number of corrections after publication does not rise.
Prevent: keep a written list of which page types need which approvals, and treat any extra reviewer as an exception someone has to justify.
No plan for what comes next
Without pillars and a calendar sized to capacity, each week begins with a debate about topics, and pieces start late because nobody agreed them.
Fix: derive a small set of pillars from goals and audience questions, then fill the next month in detail and the quarter in outline, following content pillars and calendar; hold back some capacity for refreshes and reactive pieces.
Verify: the time between an idea being agreed and its brief being approved shrinks, and the calendar's slots are filled before the month begins.
Prevent: run the weekly, monthly and quarterly calendar rhythms and shrink the plan whenever the same format slips twice.
Starting from a blank page every time
A team that writes a new piece for every email, social post and video spends its research and review hours over and over.
Fix: pick a few proven or central assets each quarter and build a format ladder from each, adapting rather than pasting, as the repurposing guide explains; plan the derivatives in the brief so the source is written with standalone sections.
Verify: the share of channel output that comes from existing sources rises, and the hours spent per published item fall without engagement on the derivatives dropping.
Prevent: add a repurposing decision to every brief and a quarterly review of which sources deserve a ladder.
AI drafts that cost more than they save
AI can produce a draft in minutes, but a draft prompted without the brief and sources returns generic structure and unverifiable claims, and the editor rebuilds it. Google's guidance on AI-generated content focuses on the quality of what is published rather than how it was made, so the checking cannot be skipped.
Fix: prompt from the full brief with the sources supplied, and set the review gate described in AI-assisted content with human review: a named fact-checker who did not write the prompt, a voice edit and an expert sign-off.
Verify: editing time per AI draft falls and fewer drafts are sent back at the gate.
Prevent: version the prompts that worked, record why drafts were returned, and use AI only for the content types where the record shows it saves time.
Work nobody can see
When stages, owners and due dates live in individual inboxes, a piece can stall for weeks before anyone notices.
Fix: define the stages from plan to report, give each an owner and a turnaround, and track every piece on one shared board, as the monthly content operations playbook sets out for search content.
Verify: every piece in progress shows a stage, an owner and a due date, and the number of pieces older than their planned cycle falls.
Prevent: review the board weekly and escalate anything that has not moved since the last review.
A prevention routine for a steady content line
Speed comes from a line that is planned, briefed and visible, so the routine checks those three things on a rhythm. Weekly, look at the board for anything that has not moved, ask its owner what it is waiting for, and clear the wait or escalate it the same day. In the same meeting, confirm that next week's briefs are approved, so writers never start without one. Monthly, read the stage timings for the pieces published that month and compare them with the previous month: a stage that grew is where the next fix belongs. Check that every brief carried its question, its call to actionThe prompt that tells a reader the one action to take next, such as a button or link. and its review criteria, because missing fields predict rewrites. Quarterly, review the approval list, the repurposing sources and the AI prompt record, and shrink the calendar if the team has missed slots for the same format more than once. Google's helpful content guidance asks who created a page, how and why; a line that keeps a brief, a review record and a named owner for every piece can answer all three without slowing down.
An agency blog finds its real bottleneck
A marketing agency planned 8 articles a month and was publishing 3. A trace of the last 10 published pieces showed an average of 41 days from idea to publication, of which 6 were spent writing. Review took 19 days on average, with up to 5 people commenting and 4 rounds of changes, and 4 of the 10 drafts had been rewritten in full because the brief was a title and a keyword. The agency named one editor and one subject reviewer per pillar, made the managing director an approver only for pages quoting client results, and required a reviewed brief before any writing slot. Over the next quarter the average cycle fell to 17 days, review to 5, and output rose to 7 articles a month with the same two writers.
Common mistakes
Hiring writers when the queue is in review. Letting anyone who comments block publication. Briefing a title and a keyword. Planning only the week ahead. Writing every channel's version from scratch. Treating AI drafting time as the saving while the review time grows unseen.
