What's the Difference Between UI and UX Design?

Clients mix these two up constantly, and to be fair the industry doesn't help, half the job ads out there ask for a "UI/UX designer" as if it's one word. It matters though, because when a website underperforms the fix usually sits in one discipline or the other, and knowing which one saves you paying for the wrong thing.

UX design is the working-out. How the site is structured, what order things come in, what a visitor has to do to get from landing on the page to filling in the form, and how much thinking you're asking them to do along the way. UI design is the surface. The type, the colour, the spacing, the buttons, what things look and feel like when you touch them. UX is the thinking, UI is the finish.

The comparison that gets wheeled out in every article on this subject is a house: UX is the floor plan, UI is the paint. It's a cliché because it works. A badly planned house is miserable to live in no matter what colour you paint it, and a well planned one still feels unfinished if nobody bothered with the decorating. Websites are the same. We've had people ask us to "make it pop" when the problem was that nobody could find the contact form. That's not a paint job, that's a floor plan issue.

What UX work looks like

Less glamorous than people expect. It's interviews and surveys to find out what visitors are trying to do. It's sitemaps and rough grey wireframes with no colour in them at all, which always disappoints somebody in the room. It's watching a real person try to complete a task on a prototype and discovering they never scrolled past the second section, which stings, and then reordering the page because of it. The output is structure: journey maps, wireframes, test notes, a plan for where everything goes and why.

Good UX work is mostly subtraction. Fewer form fields, fewer steps to checkout, fewer decisions per screen. If a designer's proudest moment on a project is something they removed, that's usually the UX person.

What UI work looks like

This is the part everyone pictures when they hear "design". Typefaces and type scales, colour palettes that don't fight each other, spacing, button states, the little bits of motion when a menu opens. A UI designer takes the grey wireframe and turns it into something that looks like your brand and feels finished. They're also the ones checking colour contrast so text stays readable for everyone, and making sure the whole thing holds together on a phone screen.

Where it goes wrong

You've seen both failures. The site that's gorgeous but you cant find the pricing page. And the site that works perfectly well but looks like it was built in 2011, so you quietly doubt the company behind it. The first is UI without UX, the second is UX without UI. Neither survives contact with a real visitor for long.

One concession: at small business scale the split is a bit academic. You're rarely hiring two separate specialists for a brochure site, one designer does both, and plenty do both well. The distinction starts to earn its keep on bigger builds, products, apps, anything where research and testing change what gets built. Then you want someone whose whole job is the thinking and someone whose whole job is the finish.

Which one do you need?

If people land on your site and leave without doing anything, start with UX. If they stay but the site makes your business look smaller or older than it is, start with UI. And if you're commissioning a new build, ask whoever you're talking to how they handle each. If the answer is a blank look, keep shopping.