When production grinds to a halt
In an editorial team, quality is almost never the first problem. The first problem is regularity. A blog that publishes in bursts then disappears for three months, a site that depends entirely on one person, a newsroom that no longer knows what's in progress, what's approved, what's late β that's the daily reality of most teams.
A good workflow doesn't make people write better. It makes them write more regularly, without quality collapsing.
The four essential stages
1. Detection
The moment an idea emerges. This idea may come from trend monitoring, a commercial request, an editor's intuition. Whatever the source, it must be formally captured: a working title, a reason to write, a target audience. Without this capture, the idea is lost.
2. The brief
The brief is the move from idea to assignment. It specifies the angle, sources to consult, length and tone constraints, and the deadline. A vague brief produces a vague article. A precise brief saves three times the time it took to write.
What a good brief contains
- Working title and a one-sentence reason to publish now
- Audience: who it is for, and what they already know
- Angle: the specific question the article answers
- Sources: documents to consult and people to contact
- Format: target length, structure, visuals needed
- Tone and constraints: style notes, legal or brand sensitivities
- Deadline and approver: when it is due and who signs off
3. Writing
The most visible stage but often the least decisive in terms of team productivity. A writer with a good brief writes twice as fast. A writer without a brief writes, rewrites, doubts, loses momentum.
This matters even more with AI assistance. When a first draft can be produced from a brief and its sources, the draft is only as good as the instructions behind it. The time saved on the first version should go into the brief and the review.
4. Publication
Once approved, the article must reach its channel(s): main site, secondary site, newsletter, social. Multiplying channels multiplies the value of work already done β provided you don't redo everything every time.
A worked example: an agency running three client blogs
Imagine a small content agency with four writers and one editor, handling blogs for three clients: a logistics company, a regional bank and a software vendor. Before organising its workflow, the agency runs on a shared inbox and a spreadsheet. Ideas arrive by email, writers pick whatever appeals to them, and the editor discovers on Friday that two clients have nothing scheduled for the following week.
After a few weeks of restructuring, the same team works differently:
- Every idea, whatever its origin, goes into one backlog with a client tag, a working title and a reason to write.
- Each Monday, the editor turns the strongest ideas into briefs for the week, each with a deadline and a named writer.
- Writers work only from briefs. When a brief is unclear, they ask before writing.
- Each client has its own calendar and its own approver, so a delay at one client doesn't hold up the other two.
- Newsletter items and social posts are adapted from the approved article instead of being written from scratch.
The writers are the same people with the same talent. The difference is that nothing sits in an inbox waiting for someone to notice it.
Classic pitfalls
The human bottleneck
In many teams, one person validates everything. When this person is on holiday or overloaded, production stops. A robust workflow always plans a backup path or clear delegation.
The late brief
A brief written after writing has started is almost always worse than one written before. Yet, in a rush, that's what happens. The discipline of an upfront brief is one of the best editorial investments.
Tool sprawl
Google Docs to write, Notion to plan, chat to validate, the CMS to publish, Excel to track performance. Five tools, five places where information can get lost. Workflow coherence is often worth more than the sophistication of each tool taken in isolation.
The invisible status
If you have to message a colleague to find out where an article stands, the workflow has a gap. Status should be visible to everyone involved without a meeting or a chat thread.
Multi-site: the partitioning challenge
When several sites coexist within the same team, each with its editorial line, author rights, calendars, the risk is to mix what shouldn't be mixed. A good multi-site workflow guarantees that:
- Each article clearly belongs to one site
- Permissions reflect actual roles
- Each site's calendar is readable separately
- Performance analytics aren't muddled together
The rule is simple: what separates sites in strategy must also separate them in tooling.
Setting it up in one week
- Day 1: map the current flow. Write down where ideas come from, who approves what, and where articles get stuck. Be candid; the point is to find bottlenecks.
- Day 2: define statuses. Keep them few and explicit, for example: idea, briefed, in writing, in review, approved, published.
- Day 3: write a brief template and agree that nothing goes into writing without one.
- Day 4: name backups. For every approval step, name a second person who can approve when the first is away.
- Day 5: set the cadence. Agree on a weekly planning slot and a publication rhythm you can actually sustain.
Review the setup after a month. Fix what doesn't work before adding new steps; most workflows fail from too many stages, not too few.
Key takeaways
A good editorial workflow:
- Systematic capture of ideas, from every source, in one place
- Explicit briefs before writing
- Few, visible statuses so nobody has to ask where an article stands
- Multi-channel publication without duplication
- Clear roles and backup paths
- Multi-site partitioning where it exists
The rest is rigour over time. And rigour over time is what turns a blog into a media outlet.