UX vs UI vs Product Design: Differences Explained
UX design decides how a product works for a person. UI design decides how that behaviour looks and responds on screen. Product design decides what the product is, which problem it solves, and how it earns its place. The three overlap, and in small teams one person does all of them. The distinction matters when you hire, scope or review work.
UX: how it works for the person
UX work starts with research and ends with a flow that people can complete. It covers the user's goals, the order of tasks, the information they need at each step, and the recovery path when something goes wrong. The outputs are research notes, journey maps, task flows, and usability findings.
A UX question sounds like: 'Why do people abandon the address step?' or 'What does a new merchant need to see first?'
UI: how it looks and responds
UI work turns the decisions into interface elements: layout, typography, colour, components, motion and feedback. It makes sure a button looks clickable, that errors appear where the user is looking, and that the system behaves the same way across screens. The outputs are visual designs, component libraries and interaction specifications.
A UI question sounds like: 'How should this table handle long Arabic names?' or 'What does a disabled state look like on mobile?'
Product design: what the product is for
Product design sits above both. It asks which users to serve, which problems matter most, which features the first release needs, and how success will be measured. It works with business constraints, engineering capacity and the market. Product designers usually own the flows and the interface, but they also shape the scope.
A product question sounds like: 'Should the first release include invoicing, or only the booking flow?'
A comparison
| UX design | UI design | Product design | |
|---|---|---|---|
| Core question | How does it work? | How does it look and respond? | What should it be? |
| Main outputs | Flows, research, usability findings | Components, visual design, states | Scope, priorities, flows, success measures |
| Typical tools | Interviews, analytics, prototypes | Design systems, prototypes, specs | All of the above, plus roadmap inputs |
| Who it serves most | The user | The user and the brand | The user, the business and the team |
Why the labels get confused
Job titles were invented quickly, and companies use them differently. A 'UX designer' at one company runs research and designs screens. At another, the same title means a visual designer for a marketing site. Read the job description and look at the work examples, not only the title.
How the three work together
A healthy product team uses all three perspectives in sequence. Product design frames the problem and the scope. UX design defines the paths and checks them with users. UI design makes the paths consistent and easy to build. Feedback should flow in both directions: UI problems can reveal UX gaps, and UX research can change the product scope.
If one of the three is missing, the product usually shows it. Missing UX produces features nobody can finish. Missing UI produces screens that do not match. Missing product design produces a polished product with the wrong scope.
What to ask when you hire
Ask a candidate to explain a recent decision in each of the three areas. The answers reveal which perspective they start from and where they are strongest. Then match that to the need you actually have this quarter.
Next step
Get help improving conversion
Send me the page or flow that loses people. I will tell you where the friction is and what to change first.
Open the conversion page