UX design — short for user experience design — is the practice of making a product usable, useful and coherent. It’s concerned with how something works: who uses it, what they’re trying to do, and the path that gets them there with the least friction. Good UX is mostly invisible; you only really notice it when it’s bad.
Put simply: UX design is the difference between a product people understand in seconds and one they abandon in frustration — and that difference is decided long before the visuals, in how the problem is framed and the flow is structured.
What does a UX designer do?
A UX designer figures out how a product should behave, then designs it so people can actually use it. Day to day that spans a few distinct kinds of work:
- Research — interviews, testing and analytics to understand real behaviour and needs
- Information architecture & flows — how the product is structured and how people move through it
- Interaction & interface design — the screens, states and micro-interactions
- Prototyping & usability testing — validating decisions before engineering builds them
UX design vs UI design
The two are often confused. The simplest distinction: UX is how it works; UI is how it looks and feels. UX decides the structure and flow of, say, a checkout — how many steps, what’s asked and when. UI makes each step legible, the primary action obvious and the whole thing feel trustworthy. You need both, and they’re usually done together. We unpack the difference in full in UI vs UX.
How UX design works — the process
UX design isn’t a burst of inspiration; it’s a repeatable process. In short: understand the problem and the user, define what to build, design the flows and interface, prototype and test with real people, then iterate. Each step de-risks the next — skip research and you design on assumptions; jump to visuals and you polish the wrong thing. The full walkthrough is in our guide to the UX design process.
Why UX design matters
Because usability is a business outcome, not a nicety. Clear UX lifts the metrics that matter — sign-ups, activation, conversion, retention — and lowers support load, because people don’t get stuck. It’s also cheaper to get right early: fixing a flow in a prototype costs a fraction of fixing it after engineering has built it. Good UX is one of the highest-leverage investments a product team can make.
Getting started with UX
If you have a product already, the fastest way to see where UX is helping or hurting is a structured UX audit — expert review plus your data, returned as a prioritised list of fixes. If you’re building something new, UX belongs at the start, shaping what you build before a line of code is written. Either way it’s a craft worth doing properly: senior people, real research, and a process that earns each decision.
