Most Design Feedback Is Opinion Wearing the Costume of Expertise¶
"Users won't understand this." Said flatly, in a review, by someone with the title or the tenure to say it without being questioned. It sounds like a finding - specific, confident, delivered in the language of expertise. It's usually a guess, and the tell is simple: ask "what's that based on," and most of the time the honest answer is nothing more concrete than a feeling, dressed up in the vocabulary of professional judgment because that's how feedback is expected to sound in a room like that one.
The Costume, Specifically¶
Real expertise and a confidently-delivered guess look identical from the outside, because both get expressed in the same register: short, declarative, delivered without hedging. "This will confuse users" and "this tested poorly with three of the five people who tried it" read as equally authoritative on the page - the difference only shows up if someone asks what's underneath the sentence, and in most rooms, nobody does, because asking feels like challenging the person's competence rather than just asking a normal clarifying question.
This is precisely why bad feedback survives so well in design reviews. It's not that people can't tell the difference between evidence and opinion in the abstract - it's that the social cost of asking "how do you know that" in the room, out loud, to someone senior, is higher than the cost of just accepting the statement and moving on. The costume works because unmasking it feels confrontational, not because anyone's actually fooled.
Why This Particular Failure Mode Is So Durable¶
Vague feedback can't be disproven, which makes it feel safer to deliver. "This feels off" or "I'm not sure users will get this" commits to nothing specific enough to be checked against anything, which means the person delivering it never has to be wrong later - a specific claim like "this label will get misread as a discount code" can be tested and shown false; a vague unease never can be, which quietly makes vague feedback the lower-risk thing to say even when it's the least useful thing to hear.
Seniority substitutes for evidence, by default, unless something displaces it. In the absence of any other basis for a claim, "this person has shipped a lot of products" becomes the implicit justification for trusting their guess over someone else's - which is a real, sometimes reasonable heuristic, but it's still a heuristic standing in for evidence, not evidence itself, and it fails exactly in the cases where the senior person's pattern-matching happens to be wrong for this specific audience.
Nobody wants to be the person who asks for proof of a feeling. Requesting evidence behind a piece of feedback can read as adversarial even when it's asked in good faith, which means most teams develop a norm of accepting stated opinions at face value rather than routinely asking the one question that would separate real signal from a confident guess.
What Separates a Real Finding From a Guess¶
A real finding names a specific reaction, from a specific person or group, to a specific thing - "3 of 5 participants tried to tap the logo expecting it to go home" is falsifiable, attributable, and reproducible in a way "I don't think this is intuitive" never is. If a piece of feedback can't be traced back to an actual observed reaction from someone who isn't in the room giving the feedback, it's an opinion - possibly a well-informed one, but an opinion, and worth treating as input to weigh rather than a verdict to comply with.
Making the Distinction Normal, Not Confrontational¶
The fix isn't training everyone to distrust each other's feedback - it's making "what's that based on" a routine, low-stakes question rather than a challenge. Teams that build the habit of asking it as a matter of course, on every piece of strong feedback regardless of who delivered it, stop treating the question as an attack on the person and start treating it as a normal part of how feedback gets processed - which is also exactly the habit that makes a team reach for a quick round of real user reaction instead of relitigating the same opinion a second and third time.
FAQ¶
Isn't experienced pattern-matching sometimes right even without a specific test behind it?
Often, yes - experienced judgment is a real, useful signal, not something to discard. The issue isn't that judgment-based feedback is worthless; it's that it should be labeled as judgment rather than presented with the same confidence as an actual finding, so the room knows which kind of input it's weighing.
How do you ask "what's that based on" without it sounding like a challenge?
Frame it as information-gathering, not disagreement - "is that from something specific we've seen, or your read on it" is a genuinely neutral question that most people can answer honestly without feeling accused of anything.
What if the person giving vague feedback is the one who signs off on the project?
That's exactly the case where a quick, real test matters most - it turns "I have a bad feeling about this" into a specific, checkable question, which tends to resolve faster and with less friction than an extended debate about whose instinct to trust.