The Metric That Predicts Editorial Burnout Before It Happens

Most editorial teams don't collapse suddenly. They erode. The warning signs are there months before anyone admits something is wrong—they're just not the ones leadership is watching.

The standard metrics are useless for predicting burnout. Output looks fine. Deadlines are met. Publish rates hold steady. Then one Tuesday, your best writer emails that they're done, or your editor stops responding to Slack, or someone takes medical leave and doesn't come back. By then, the damage is already structural.

The metric that actually matters is revision density per writer per week—the number of editorial passes a single piece goes through before publication, measured against the person who wrote it.

This isn't about quality control. This is about invisible workload accumulation.

What Everyone Gets Wrong

Most teams assume revision cycles are a sign of rigor. More passes mean better editing, which means better content. This is true up to a point. But there's a threshold where revision density stops being quality assurance and becomes a symptom of systemic dysfunction.

When revision density climbs above 3.5 passes per piece for a single writer, you're not looking at editorial excellence. You're looking at one of three things: unclear briefs that force rewrites, editorial indecision that compounds across rounds, or a team so stretched that feedback arrives late and requires substantial rework.

The writer experiences this as invisible labor. The piece is "done," but it isn't. They move to the next assignment while waiting for feedback. Then feedback arrives requiring 40% rewrite. They're now juggling two pieces in active revision. A third brief lands. The cognitive load compounds silently.

Revision density is the metric that captures this because it's objective and it's tied directly to individual capacity. A writer handling five pieces with 2.2 revisions each is operating normally. That same writer handling five pieces with 4.1 revisions each is drowning—but their output count looks identical.

Why This Matters More Than People Realize

Editorial burnout doesn't announce itself through missed deadlines or dropped quality. It announces itself through attrition. And attrition is expensive: replacement hiring, onboarding lag, institutional knowledge loss, and the temporary collapse of editorial momentum while you rebuild.

Revision density predicts attrition because it's a direct measure of whether a writer's cognitive load is sustainable. High revision density means the writer is spending more time in reactive mode (responding to feedback, reworking sections) than generative mode (thinking, researching, writing). This is exhausting in ways that aren't visible in sprint reports.

The second reason this matters: revision density reveals process problems that output metrics hide. If your average revision density is 3.8 passes across the team, that's not a writer problem. That's a brief problem, an editorial decision-making problem, or a feedback-timing problem. These are fixable. But you have to see them first.

Teams operating at scale often don't. They see writers leaving and assume it's compensation or opportunity. Sometimes it is. Often, it's that the writer spent six months in a state of perpetual rework and finally ran out of patience.

What Actually Changes When You See It Clearly

Once you're tracking revision density by writer, the interventions become obvious. If one writer's density is 4.2 while the team average is 2.8, you don't assume they're a weaker writer. You audit their briefs. You check when feedback is arriving. You look at whether editorial decisions are being made decisively or whether pieces are cycling through multiple rounds of conflicting notes.

You also get early warning. A writer whose revision density climbs from 2.4 to 3.6 over eight weeks is signaling distress before they resign. That's your window to intervene—to reduce their load, to fix the process creating the rework, or to have a real conversation about capacity.

For teams scaling editorial operations, this becomes foundational. You can't manage what you don't measure. Output metrics tell you what got published. Revision density tells you whether the people who published it are still going to be there next quarter.