On clarity vs. brevity

In UX writing, there’s this sneaky habit of conflating clarity and brevity like they’re the same thing. They’re not. Clarity is about making sure someone gets it, no questions asked. Think of a line like, “Enter your email to reset your password.” It’s straightforward, almost idiot-proof. Brevity, though? That’s the art of slashing words down to the bone—“Email for password reset.” Tight, sure, but does it work?

Here’s the rub: we writers assume short equals clear. It’s a trap. I’ve seen it too many times—teams obsessed with trimming fat, thinking they’re doing users a favor. But “Reset via email” sounds cool and crisp until you realize it’s a riddle. Does it mean to type your email here? Check your inbox? Pray to the tech gods? Users don’t need puzzles; they need a lifeline, especially when something’s gone wrong, like a failed login or a crashed checkout. That’s when brevity can betray you—saving syllables but losing clarity.

This isn’t just semantics. It’s about how we respect people’s time and attention. Clarity takes the lead because comprehension isn’t negotiable; brevity’s just a sidekick, useful when it doesn’t muddy the waters. I’ve learned this the hard way—writing’s not about flexing how clever you can be with fewer words. It’s about being useful. Next time you’re crafting a button label or an error message, ask: “Will they get it?” Not, “Can I make it shorter?”