The advocate's trap
There’s a version of user advocacy that starts well and ends badly. The designer takes the role seriously. They push back when something feels wrong. They speak up in rooms where no one else is representing the user.
And somewhere between week one and month eighteen, without quite noticing it, they become the person who always says no. The friction. The person whose objections get managed rather than considered.
The question you might reasonably ask at that point - how do designers stay the voice of the user without suffering that fate - contains a trap. It assumes chronic dissent and genuine advocacy are the same thing. They aren’t. One is failure dressed as principle.
Designers with real influence can afford to argue loudly for users because they’ve already done the work to understand what’s viable before the disagreement starts.
They know the engineering constraints. They’ve read the commercial context. They’ve sat through enough budget meetings to know where the real pressure points live. When they push back, it’s not a reflex or a values statement. It’s a diagnosis.
This is infrastructure work. Hours in conversations, meetings and documents that no other designer will ever see. None of it looks like design. All of it is what makes design influence possible. Without it, you’re arguing from the outside. The person who shows up to a room where three other functions have already aligned and offers resistance without standing. That resistance gets filed under “design being difficult” and the next time the room gets smaller by one.
Not everything deserves the same energy. There are decisions genuinely worth holding the line on - a flow that exploits users to hit a metric, a pattern that trades long-term trust for short-term conversion. These exist. Most things are not these things. Most things are suboptimal: a priority call you’d have made differently, a constraint you wouldn’t have accepted. Those are not wrong. Treating them as wrong is what turns advocacy into noise.
The judgment required to distinguish between wrong and merely suboptimal is itself a design skill. It doesn’t come from values. It comes from looking at enough product decisions over enough time and developing a calibrated sense of what actually matters.
“Users won’t like this” is exhausting to hear. It’s unfalsifiable, offers nothing to work with, and signals that the designer hasn’t done the diagnostic work and is instead offering opinion disguised as empathy. A useful objection names the failure mode specifically: users will attempt X, the current design punishes them for it, the cost will show up in Y. It gives the other people in the room something to respond to. An observation almost always beats a position.
The credibility that makes advocacy work accrues quietly and incrementally. It comes not from being right, but being right in the moments that mattered. After enough of those moments, the dynamic changes. Pushback from someone with that track record is heard differently.