What I learned managing a content team

I built the content pipeline at a writing agency and then spent eighteen months running it. Assigning writers, editing drafts, turning client briefs into work people could actually execute, and shipping on time.

Most of what I learned was not about writing at all.

The brief is the whole job

Nearly every problem I dealt with downstream began as a vague brief upstream.

A writer who "missed the point" had usually been given no point. A draft that came back in the wrong tone had usually been commissioned without a tone. When I fixed my briefs, half my editing load disappeared, which told me exactly whose fault it had been.

A brief that works answers seven things:

• Who is reading this, and what they already know
• What they should be able to do after reading it
• The rough structure, in headings
• Sources you expect to see used
• Word count and deadline, both of them real
• The one claim that must be true when it is finished
• What this is not — the tempting tangent you do not want

That last line prevented more rewrites than everything above it combined.

Say the hard thing in draft one

Feedback debt compounds faster than any other kind.

If a piece is broken at the structure level and you write "looks good, minor notes," you have just bought two more rounds and a writer who will feel ambushed in round three. Softening round one protects nobody. It moves the difficult conversation to the point where it costs most.

"Kind and clear are the same thing on a deadline. It is vague and late that people find insulting."

Say it in the first round, say it specifically, and describe what a fixed version would look like.

Edit the piece, not the writer

I split notes into two piles and send them differently.

Developmental notes — this argument does not hold, this section is in the wrong place, the intro makes a promise the piece never pays — go in a short message at the top. Line edits go in the document, tracked, without commentary.

Mixing the two is what makes feedback feel like an attack. Thirty inline comments about commas reads as thirty problems, when there was one problem and twenty-nine commas.

Lateness is usually a system problem

When one writer is always late, look at the person. When several are, look at yourself.

Check the assignment load first, then the quality of the brief, then the deadline you set while feeling optimistic on a Monday morning. The writer is the last place the fault usually lives and the first place everyone looks.

Protect the cadence, not the heroics

A team that ships four solid pieces a week for a year beats a team that ships nine in a burst and then collapses for a fortnight.

Clients feel rhythm more than volume. Writers feel it more still. The week everybody pulled a miracle is the week to worry about, because you have just taught the client to expect miracles.

What I got wrong

I over-edited for the first few months.

I rewrote drafts into my own voice because it was quicker than explaining what was off. It produced clean copy and two expensive side effects. Writers stopped taking risks, and I became the bottleneck the whole pipeline waited on.

The fix was uncomfortable and obvious. Let a piece go out at eighty-five per cent in the writer's voice rather than a hundred in mine. Within two months the eighty-five had become ninety-five without my help, and I had my afternoons back.

---

Content operations is mostly this. Write the brief properly, say the true thing early, protect the rhythm, and get out of the way of people who can do the job. The writing itself, by the time you reach it, is nearly the easy part.