Running Editorial Operations for Up to 35 Writers/Editors

A single-author site can keep its point of view in one person’s head. A network publishing every day across five desks can’t. As the team grew, remote writers brought different research habits and different assumptions about what readers already knew. Volume and quality pulled in opposite directions, and “write it like I would” doesn’t scale.

• Recruiting and onboarding for a distributed team that reached up to 35 writers/editors at peak.
• Content briefs that spell out audience, search intent, angle and what the piece should not try to be.
• Review cycles with clear checkpoints and a shared definition of “done,” so editing wasn’t a matter of taste.
• Editorial feedback, not just accept/reject: writers got specific notes so they improved over time.
• Assignment and update workflows across time zones, including ownership of older articles, not just new ones.
• A working-editor role for myself: I kept writing and editing (3,000+ articles under my own name) so standards stayed grounded in the actual work.

• Up to 35 writers/editors managed at peak, fully remote
• Continuous publishing across five publications from one set of operating habits
• 6,000+ articles across the network, a library big enough to need governance as well as production

A single-author site can hold a point of view in one person’s head. A network that publishes continuously cannot. The work had to become teachable: who writes, what a brief contains, how review works, and what “done” means.

Volume and quality pull in opposite directions. Remote contributors also pull toward inconsistency — different habits, different research depth, different sense of what the reader already knows. The operation needed structure without becoming a content mill.

Recruited, managed and edited a distributed team of up to 35 writers/editors. Set standards, assigned work and remained a working editor.

• Hire for judgment and clarity, then teach the publication’s point of view rather than a generic style sheet alone.
• Use briefs to lock audience, intent, angle, and what the piece should not try to be.
• Keep review cycles short enough to ship and strict enough to catch thin research or muddy structure.
• Mentor contributors with direct editorial feedback instead of only accepting or rejecting drafts.

• Recruited and managed up to 35 writers/editors at peak.
• Assigned work against calendars that mixed evergreen library-building with timely coverage.
• Edited for accuracy, sequence, and voice so a reader could act on the piece.
• Balanced speed with quality when news or product changes created real reader demand.

• Content briefs and assignment workflows
• Editorial guidelines and review checkpoints
• Remote collaboration across time zones
• Quality-control and update processes for a living archive

• Standards are how a point of view survives contact with more than one writer.
• Mentorship is operational: better briefs and better feedback reduce rework.
• Remote work is manageable when the workflow is explicit and the editor stays close to the writing.