Find True UX Expertise in a Sea of Self-Proclaimed Experts
Salma Abulaban
July 26, 2026
Updated on:
July 26, 2026
You can tell real UX expertise from noise by how it handles certainty. Genuine expertise tends to sound less certain, not more, because most design questions honestly start with "it depends." LinkedIn is just where that noise is loudest, a feed of confident verdicts about the one "correct" design. The same gap shows up in a pitch, a sales deck, or a hire: presentation standing in for substance, and whoever hires on the polish pays for what's missing underneath.
On LinkedIn, though, everyone is a UX expert. The feed is filled with confident verdicts about which layout wins and which design is "correct." Much of that is presentation standing in for substance.
And the people who pay for the gap are the ones who hire on the strength of a polished deck. Some arrive at Vardot impressed by a past vendor, only to find they were oversold.
Quick answer: You can tell real UX expertise from LinkedIn noise by how it handles certainty. Genuine experts separate the few UX questions that are factual, like meeting WCAG accessibility standards, from the many that are contextual, and they say "it depends" where it honestly does. Noise sells one-size-fits-all confidence and jargon. Real expertise explains things simply, names the limits of its own advice, and leaves you able to make the next decision yourself.
What Does LinkedIn Get Wrong About UX?
LinkedIn flattens UX in two opposite directions. It turns settled, testable questions into matters of taste, and it turns genuinely context-dependent questions into universal rules.
Both moves strip away the one thing that makes UX work: context. A hot take travels well precisely because it drops the caveats, and the caveats are usually where the real expertise lives.
The distinction that matters most is between two kinds of UX questions, because they call for opposite responses:
Question type
Example
How it gets settled
Factual
Does this text meet WCAG AA contrast? Is this control keyboard-accessible?
Measured against a standard. A contrast checker gives a pass or fail. Not up for debate.
Contextual
Which form layout converts? Button or text link here?
Tested with your actual users. Research gives a default, not a verdict.
Which UX Questions Are Factual, Not Opinion?
A handful of UX questions have settled answers, and accessibility is the clearest of them. Under WCAG 2.2, the W3C's Web Content Accessibility Guidelines, Level AA requires a contrast ratio of at least 4.5:1 for normal text (Success Criterion 1.4.3).
You can check that ratio with free tools in seconds. There is no gray area. A pair of colors either clears the threshold, or it doesn't.
What I keep seeing on LinkedIn is people turning that kind of factual question into a debate about taste. A thread fills up with, "but I really like this one" and "I think this reads better," when the real problem is that the design fails accessibility. That is noise dressed as expertise.
Which UX Questions Are Contextual and Have No Single Right Answer?
Most UX questions are contextual rather than settled, with no single correct answer. Take form layout.
There is well-circulated research, the kind associated with sources like the Nielsen Norman Group, that generally suggests using the priority position on the left for left-to-right languages, and that generally favors buttons over text links when you want to draw attention. Those are useful defaults. They are not verdicts.
The moment you post one of them, as a rule, you have dropped the context that decides whether it holds. Every case is different. When I run user testing, before or after a launch, the results keep failing to match my assumptions.
Users do not behave uniformly, and even research-backed “best practices” can be deemed “second best” by different sets of users. I have watched my own parents use a site where the button looks obvious to me, and they still miss it, or the type I considered comfortably readable turns out to be too small for them.
Widely circulated research is a starting point, not a substitute for watching your actual users. My problem with LinkedIn is that it takes findings out of context and posts them as if UX were one-size-fits-all. It never is.
You can tell real UX expertise from LinkedIn noise by how someone does the work. Doing the work means three things at once:
Abiding by the factual do's and don'ts that have settled answers
Applying best practices in the grey areas where no single answer is right
Staying open to changing course when your users' behavior or user testing says you should
That is a proper UX mindset, and it tends to sound less certain than LinkedIn, not more, because it treats most design questions as contextual and holds even its best practices loosely enough to revise them. The noise sells the opposite: confident verdicts about the one "correct" design, presentation standing in for substance, and the people who hire on a polished deck paying for the gap.
Why Does This Happen More in UX Than in Engineering?
UX attracts presentation-as-expertise more than backend engineering does, and the main reason is exposure. UX designers usually work in client-facing roles, and many engineers don't.
Put people in front of clients often enough, and the incentive to perform expertise, rather than demonstrate it, shows up more. There has been a real shift here, though.
Many clients now understand that UX is not just the interface, that there is research behind it, even if they can't yet name what that research is. The trouble is how we got them there.
Designers spent years explaining that "looks nice" and "works" are not the same thing. Somewhere in that explanation, we overcomplicated it. The actual activities in UX are straightforward: you talk to people, you send out surveys, you watch someone use the thing.
The depth lies in critical thinking and accumulated experience that let you understand why something is happening, not in the mechanics. Because the mechanics look simple, some practitioners overcompensate with vocabulary.
Focus groups, stakeholder interviews, and user interviews are largely the same activity: listening to people carefully. What differs is who is in the room.
Properly labelling UX activities is fine, and often useful. Using the labels to lose a client is not. Some "experts" started weaponizing the terminology, betting that a client who doesn't follow the words won't ask enough questions to discover that the work was, at bottom, a careful conversation with people.
UX got portrayed as something that cannot be understood. It can. This isn't every designer, and a client-facing engineer can fall into the same habit; it simply shows up more often where client-facing exposure is highest.
Real Expertise Simplifies and Leaves You More Capable
The tell of real UX expertise is not confidence. It's closer to the opposite. The loudest advice sells certainty and vocabulary, while substance simplifies.
That inversion is a reliable filter, because it is hard to fake. You can perform confidently, but you cannot simplify a topic you don't actually command.
The deeper cost of getting this wrong is not a weak deliverable. It's a dependency. The client is sold in the moment and left hooked, able to trust the person but not to make the next decision without them.
No client comes back for every small choice, so the gaps compound into avoidable decisions stacked on top of one another. Strong communication genuinely matters. Expertise you can't share is nearly as limited as a presentation with nothing behind it.
But a real expert aims to hand over the part of their judgment that is relevant to you, so you leave more capable, not more reliant. This is why we treat the accessibility line as non-negotiable in the nonprofit and public-sector work we do at Vardot. When the standard is testable, "it depends" isn't an acceptable answer.
How Do You Tell Signal From Noise When You Hire UX?
You can separate real UX expertise from a good presentation with a short set of tells. Each is based on something a genuine expert does that a skilled presenter can't fake.
They can explain it simply. A real expert bridges the gap between their knowledge and where you stand and speaks your language. If someone can't explain something simply, they probably don't understand it well enough, and if you keep asking and still don't follow, the problem may not be you.
They separate the factual from the contextual. They won't argue accessibility or contrast as a matter of taste. And they won't hand you a contextual call dressed as a universal rule.
They give you actionable next steps and name the limits. After the research, can they recommend something specific, and tell you its limitations and what to watch for? A wide, impressive process with no clear "what now" often means they didn't reach the core.
They investigate the "why," not just your stated ask. Most clients arrive with an idea of what they need. A real expert keeps asking where that need came from, because if they build on your surface request, you don't get a solution; you get another layer stacked on the issue you already had.
They leave you more capable, not more dependent. You should walk away with knowledge that sustains your next decision, not just trust in this one. If the engagement leaves you unable to move without them, that's the tell that you bought a presentation.
None of these requires you to know UX yourself. They only require you to notice whether the person in front of you is making the work clearer or keeping it ambiguous.
Work With UX That Leaves You More Capable
A real expert investigates the “why” behind your request, tells you plainly which guidelines are non-negotiable and which are contextually dependent, and hands you the judgment you need to decide.
That is the standard we hold our own design work to at Vardot, especially in the nonprofit and public-sector projects where accessibility is a hard requirement, and the wrong call has real consequences for real people.
If you want a second read on a design partner, or a single design decision, from a team that leaves you more capable than dependent, let's talk.
UX
UX/UI
Design & User Experience
About the Author
Salma Abulaban
Design Team Lead
Salma is an NN/g Certified design expert and the Design Team Lead at Vardot. She has managed the delivery of research and design deliverables across 20+ projects. A natural collaborator, Salma bridges the gap between business objectives, design solutions, and development execution delivering experiences that are not only visually compelling but also strategically effective and accessible to all users.
A real UX expert can explain their thinking simply, separates factual questions (like accessibility compliance) from contextual ones, gives specific next steps along with the limitations of that advice, and investigates why you need something rather than taking your request at face value. The clearest tell is that they leave you more capable of making the next decision, not more dependent on them.
No, UX is not graphic design. Graphic design concerns how something looks; UX concerns whether people can actually use it to accomplish a goal, which is determined through research such as user interviews, surveys, and watching real users. The activities are straightforward, but the expertise is in the critical thinking that interprets why users behave as they do.
UX best practices shared on LinkedIn are useful as defaults but unreliable as rules, because they usually drop the context that decides whether they apply. Guidance like favoring buttons over links or placing priority elements on the left for left-to-right languages reflects general research, not a verdict for your specific users. Real answers come from testing with your actual audience.
A factual UX question has a settled answer measured against a standard, such as whether text meets the WCAG AA contrast ratio of 4.5:1. A contextual UX question, such as which form layout converts best, has no universal answer and must be tested with your specific users. Treating a factual question as opinion, or a contextual one as a rule, is a sign of noise.
Presentation gets mistaken for UX expertise because UX designers are usually in client-facing roles, which rewards performing knowledge over demonstrating it. Polished delivery can sell a client in the moment even when little research sits behind it. The hidden cost is dependency: the client is left able to trust the designer but unable to make future decisions without them.
