What is the difference between UI and UX?

UX is the set of decisions about what a product does and in what order. UI is the set of decisions about how those things look and behave on screen. One is architecture. The other is material. Confuse them and you hire the wrong person for the wrong problem, then spend $8,000–15,000 on polished screens that don't change how anyone behaves.

Most advice on this conflates the two because it's written by people who do both. That confusion costs real money. A startup that hires a UI designer to fix what is actually a UX problem gets polished screens built on broken logic. I've watched this cycle repeat across more than 40 retainer engagements.

Deliverables by discipline

UX deliverables include user flow diagrams, wireframes, journey maps, usability test reports, and information architecture documents. UI deliverables include component libraries in Figma, color and typography systems, interaction states (hover, focus, disabled, loading, error), icon sets, and annotated handoff files for engineering. The overlap is prototyping, which needs both UX logic and UI fidelity to be worth anything.

Timeline is another way to tell them apart. On a typical SaaS product build, UX work runs weeks 1–4 and produces validated flows. UI work runs weeks 3–10 and produces buildable components. If you hand off a finished UX document and start UI from scratch, you'll spend 2–3 weeks re-learning decisions that should have been made together.

Here's the part most sources skip: UX errors are far more expensive to fix late than UI errors. Changing a button color in a design system takes a designer 20 minutes and an engineer 30. Changing the information architecture of a 12-screen onboarding flow after engineering has built it takes 3–6 weeks and almost always introduces regression bugs. Getting UX right before investing in UI fidelity is a financial decision, not a matter of taste.

On a McKinsey workstream we shipped in 2023, the internal product had gone through three rounds of UI refinement without anyone auditing the underlying UX. The UI looked excellent. Task completion rate for the primary workflow was 34%. A two-week UX audit found three navigation decisions that sent users into dead ends. Fixing those, then updating the UI to match the new flows, brought task completion to 71% in the next usability test cycle. Same product, same team, completely different result once the sequencing was right.

A practical test worth keeping in your back pocket: if users can't find something, that's a UX problem. If they find it but don't understand or trust it, that's probably a UI problem. Both matter. But they need different skills, different tools, and different timing. For SaaS products, where onboarding conversion and feature adoption are the metrics that actually move revenue, getting that sequencing right is the difference between a design investment that pays back and one that produces something nobody uses.

Our notes on SaaS UI/UX design subscriptions cover how we structure that work. Book a 20-min intro if you want to talk through your specific situation. For the full guide, read our ui overview.