Product design is the work of deciding what a product does, who it does it for, and what happens when someone uses it. Two things have to hold at once: someone genuinely has the problem, and solving it earns its keep for the business paying the bill. Research, flows, pixels, the argument with engineering about what ships this quarter — all of it serves those two, and so does the next version, once real usage proves the first one wrong.
It is not a stage in a pipeline. A designer who receives requirements and returns screens is an expensive illustrator — useful, but not the person who prevented the team from building the wrong thing for six months.
Most of the confusion comes from two neighbouring titles: UX and UI. Where you sit on that boundary decides whether you are in the meeting where decisions get made or the one where they get announced.
- What is product design? — article
- What EXACTLY is Product Design? 🤔 — video
- Product Design Tutorials & Advice — video
Product Design vs UX
UX design asks whether someone can complete the task. Product design asks whether the task deserves to exist.
Both care about flows, hierarchy, error states, and whether an empty screen tells you what to do next. The difference is the question one level up. A product designer argues to cut a feature that serves four per cent of users and costs three months. A product designer argues for more friction at signup because the people it turns away churn within a fortnight anyway. Those are commercial calls, made with design evidence.
In practice the titles are traded freely and plenty of job adverts mean the same role by both. Read the responsibilities, not the label. Ask who decides what gets built. If the answer is somebody else, you are doing UX whatever the advert says.
- Visit the Dedicated UX Design Roamdapux — roadmap
- Intro to UX (User Experience) | Google UX Design Certificate — course
- Product Designer vs. UX Designer: The Difference Explained — article
Product Design vs UI
UI design is the surface — layout, type, spacing, colour, components, and the dozen states a single button has to survive. It is real craft, and teams who treat it as decoration ship products that people quietly distrust without being able to say why.
Product design owns the layer underneath: which screens exist, in what order, and what the product refuses to do. Whether the destructive action is a red button or a plain text link is a UI decision. Whether anyone should be able to delete the entire workspace in one click is a product decision.
On a three-person team you will make both kinds of call before lunch, often about the same screen. The distinction still matters, because the two fail differently. A beautiful screen attached to the wrong flow cannot be rescued with more polish.
- Product design vs. UX design vs. UI design — article
- UI/UX Design vs Product Design — video