Building Editorial Operations That Survive Turnover

The moment your best editor leaves, you discover what you've actually built.

Most teams treat editorial operations like a person—a collection of habits, preferences, and institutional knowledge that walks out the door when someone does. They've documented nothing. The workflows live in Slack threads. The style decisions exist only in the mind of whoever's been doing it longest. When that person leaves, you don't inherit a system. You inherit chaos wearing a familiar face.

This is the thing everyone gets wrong about scaling editorial: they think the problem is hiring better people. It's not. The problem is building operations that don't depend on any single person being exceptional.

The teams that survive turnover—that actually accelerate through it—have made a deliberate choice to externalize everything. Not because they're paranoid about losing staff, but because they understand that a person-dependent operation is a bottleneck masquerading as efficiency. It feels fast when one person knows everything. It's actually just fragile.

Start with the obvious: documentation. Not the kind that lives in a Google Doc nobody updates. Documentation that's embedded in the workflow itself. If your editorial calendar is in a spreadsheet, you've already lost. If it's in a tool with mandatory fields, conditional logic, and automated handoffs, you've built something that enforces process. The tool becomes the teacher. New people don't need to ask what comes next—the system tells them.

The same applies to style. Every publication claims to have a voice, but most teams enforce it through osmosis. "Just read what we've published," they say. That's not a system. That's hazing. Real editorial operations codify voice into decision trees. Not rigid rules—those kill voice. But frameworks. When do we use contractions? How do we handle numbers? What's our stance on jargon? These aren't trivial questions. They're the difference between a new hire producing work that feels on-brand in week two versus week eight.

Then comes the harder part: separating the role from the person. Most editorial teams have roles that are actually just descriptions of one person's job. "Senior Editor" means "the person who does everything that doesn't fit elsewhere." That person becomes irreplaceable. Instead, define roles by specific responsibilities with clear inputs and outputs. One person owns fact-checking. Another owns headline optimization. A third owns the final read-through. These can overlap, but they shouldn't be mysterious. When someone leaves, you're replacing a function, not trying to resurrect a ghost.

This requires building redundancy into your operations. Not waste—redundancy. Two people should know how to publish. Two people should understand your analytics dashboard. Two people should be able to brief a freelancer. When turnover happens, you don't grind to a halt while someone learns. You keep moving while the new person gets up to speed.

The final piece is the hardest: creating operations that improve when people leave. This sounds counterintuitive, but it's true. When someone departs, you have a moment of clarity. You see exactly which parts of your process were dependent on their memory, their relationships, their particular way of doing things. That's valuable information. Use it. Document what you learned. Simplify what was unnecessarily complex. Automate what was manual. The next person benefits from the friction the last person experienced.

Teams that do this well don't fear turnover. They expect it. They build for it. And when it happens, they don't lose momentum—they gain it. The operation gets stronger, not weaker. The new person doesn't inherit a mystery. They inherit a machine that works.

That's the difference between editorial operations that scale and ones that just get bigger.