In short
- UX design decides how a product works for its user: the steps, the structure, and the feedback along the way.
- The core deliverables are user flows, wireframes, and prototypes, plus what testing taught you.
- Good UX is judged by whether people finish what they came to do without confusion or help.
- UI design is the visual layer on top. They are separate skills that have to agree.
Also called: User experience design, UX, Experience design, UX/UI design.
What UX design covers
UX design starts from a person and a task. Someone opens your product to do something specific, like book a class or send an invoice. The UX designer's job is to make that path short and obvious, with an easy way back when the person makes a mistake.
In practice the work spans four connected areas.
- User flows. The steps a person takes to finish a task, including the branches when something goes wrong.
- Information architecture. How content and features are grouped and labeled, from the main navigation down to a single settings page.
- Interaction design. What happens when someone taps, types, or waits. This covers feedback, confirmations, transitions, and undo.
- Research and testing. Talking to users before designing, then watching them use the design to see where they get stuck.
How the work runs
UX work is a loop. You learn what users need, propose a structure, make it testable, watch people use it, and change it. Each pass is cheap early and expensive late, so most of the loop should happen before engineering builds anything.
A typical UX loop
- 01ResearchWho the user is, what they need
- 02Flows and structureSteps, screens, navigation
- 03WireframesLayout and priority, no style
- 04PrototypeSomething people can try
- 05TestWatch real users, fix what broke
Research does not need a lab or a big budget. A few conversations with the right users, and a few recorded sessions of people trying a prototype, usually surface the problems that matter most for a first release. Usability testing covers how to run those sessions well. Choie runs the loop in code: in a prototype week, days two to four design and code one workflow together, and day five is a walkthrough and one round of revisions.
What a UX designer delivers
| Deliverable | What it shows | Who uses it |
|---|---|---|
| User flow | Every step and branch of one task | The whole team, to agree scope |
| Sitemap or navigation map | Where everything lives and what it is called | Design and engineering |
| Wireframes | Layout and content priority for each screen | Design, to settle structure before style |
| Prototype | How the flow behaves when someone uses it | Test participants and decision makers |
| Test findings | Where people got stuck and what changed | Everyone deciding what to build next |
The deliverables are a means to an end. A wireframe that never gets tested is a guess drawn neatly. What you are paying for is confidence that the flow works before anyone writes the code for it.
UX design vs UI design
The two are often written together as UX/UI, and on small teams one person does both. They are still different skills. UX design decides what is on each screen and how the flow behaves. UI design decides how it looks and responds, from type and color to the visual states of every button.
UX design and UI design
UX design
- How the product works
- Flows, structure, and steps
- Wireframes and prototypes
- Judged by task success
UI design
- How the product looks and responds
- Type, color, spacing, and states
- Final screens and components
- Judged by clarity and consistency
When budget is tight on a first release, put UX first. A plain interface over a clear flow gets people through the task. Visual polish can follow once you know the flow is right, often with the help of a design system.
Common UX mistakes
- Designing for yourself. The team knows the product too well to see what confuses someone using it for the first time.
- Skipping the unhappy paths. Error messages and empty screens are part of the experience, and new users meet them early.
- Testing too late. Testing a finished build turns every finding into rework that has to compete with new features.
- Asking users to design the fix. People are good at showing you where they struggle and much less reliable at prescribing a solution. Watch what they do, then decide.
In a Choie build, the first live link goes out on the first Friday, so UX decisions are tested on working software early. See how a project runs.
Common questions
What is the difference between UX and UI design?
UX design decides how a product works, and UI design decides how it looks and responds on screen. UX covers flows, structure, and testing, while UI covers type, color, layout, and components.
Does a small product need UX research?
Yes, though it can be small. A handful of conversations with target users and a few sessions watching people try a prototype will catch problems that would otherwise appear after launch, when they cost more to fix.
When should UX design happen in a project?
Mostly before the build, then in smaller loops during it. Settling flows and testing a prototype first is much cheaper than changing working code later. In a Choie build, the first two weeks settle flows, hierarchy, and what to build first, and design continues alongside the code after that.
What tools do UX designers use?
Most use Figma for flows, wireframes, and prototypes, plus a video call tool for interviews and tests. Some prototype in code when the flow depends on real data or device features such as the camera.