Measuring a UX writer's worth

Holding people accountable keeps the wheels turning. For a UX writer, the dream metric ties straight to business impact: dollars saved, generated, or guarded. Imagine proving a single sentence tweak sparked a million bucks in revenue. That’s the gold standard. But let’s be real—pinpointing that kind of cash flow often feels like chasing a mirage across a data desert.

So, proxy metrics step in—stand-ins like conversion rates or user retention bumps. They’re imperfect, but they hint at value without drowning us in spreadsheets. Here’s where it gets tricky: trying to isolate one writer’s contribution in a messy, interconnected team is a fool’s errand. It’s like asking which raindrop filled the bucket during a storm.

Years back, a designer pal told me their squad slashed onboarding drop-offs by 20% after rewriting a clunky flow. The win came from words, sure—but also from design, dev, and product syncing up. Who gets the trophy? The system does. Metrics like DORA (used in tech circles) get this right. They track the engine’s roar—culture vibes or code-to-production speed—not the grunt of each piston. A UX writer’s words fuel the machine, but the horsepower? That’s collective.

Chasing individual stats misses the point. Focus on what the team delivers—revenue, protection, growth—and let the writer’s craft ripple through. Numbers matter, but they’re a compass, not a microscope. Point north, measure the haul, and keep the system humming. That’s how you gauge worth without losing the plot.