UX vs UI is the wrong question.
Why the binary persists — and what senior product designers think about instead.
U X
research / strategy
U I
visual / chrome
Every junior designer has been asked to define the difference between UX and UI. Every senior designer has stopped caring about the answer.
The binary persists because it's useful for hiring panels and bootcamp curricula. It's not useful for the work.
What the binary actually obscures
UX is positioned as the strategic, research-driven layer. UI is positioned as the visual layer. The framing implies a hierarchy — UX is “above” UI, the way an architect is “above” a draftsperson.
But the work doesn't divide that way. The decision to use a single text field instead of a multi-step wizard is simultaneously a UX decision (cognitive load), a UI decision (component choice), an engineering decision (state management), and a business decision (drop-off recovery).
When you actually ship product, you don't switch hats. You make decisions that operate on all four layers at once.
The replacement frame
The framing senior product designers I respect actually use: every decision reduces to what the user is trying to accomplish, and what is the smallest surface that gets them there.
That question doesn't sit cleanly in either bucket. It eats both.
The valuable distinction isn't UX vs UI — it's outcome thinking vs output thinking. Outcome thinking starts with the metric the work needs to move. Output thinking starts with the deliverable.
A designer who can move a conversion rate is more valuable than a designer who can produce a 40-page wireframe document, regardless of which “discipline” you put on either job description.
Why the binary won't die
- It maps cleanly to org charts. UX teams and UI teams exist because procurement and HR need them to.
- It gives juniors a tractable map. Telling someone new “do user research, then design screens” is easier to teach than “develop intuition for which decisions move which metrics.”
Neither reason is about the work being good.
What to do instead
- If you're senior: don't take “are you a UX or UI designer” interview questions seriously. Reframe to outcome.
- If you're hiring: stop screening for the binary. Ask what metric the candidate has moved, and how they decided to move it.
- If you're building a portfolio: lead with outcomes, not deliverables. The work is the argument; the labels are noise.