Product Design vs UX and UI

LunchLoop delivers home-cooked tiffins from neighbourhood cooks to office workers, Monday to Friday. About one in eight tiffins comes back untouched, because changing a day's lunch means messaging support before 9 p.m. the night before. Three designers look at this. One asks whether the skip control looks right, one asks whether skipping is easy, and one asks whether skipping is even the right fix. They are all doing design, but they are answering different questions.

The rule

UI shapes the screen, UX shapes the experience, product design shapes the outcome.

UI (user interface) design is the visible, touchable layer: colour, type, spacing, buttons and their states. Its work ends up as screens and components.

UX (user experience) design is the whole path a person takes to get something done: the flow, the structure, how easy things are to find and finish. Its work ends up as flows, wireframes and tested journeys.

Product design covers both, and adds the questions around them: which problem, for whom, why now, and how we will know it worked. A product designer works closely with product managers and engineers on goals, trade-offs and metrics. The work ends up as a shipped change that moves a number someone cares about.

For LunchLoop's waste problem:

• UI: the Skip control uses the secondary button style and shows a clear locked state after the cutoff.
• UX: skipping takes one tap from the home screen instead of a chat with support.
• Product: skipping should cut untouched tiffins from 12% to 5% while revenue holds, because skipped meals turn into credit.

Job titles blur in real life. In a small team, one person does all three. The difference is the question you are answering, not the name on your badge.

The shortcut

Sort any design question by asking: "What would prove this right?"

The common trap is thinking product design is just UI plus UX. The extra part is outcome thinking: choosing the problem, weighing trade-offs and measuring what changed.

Drills

Answer fast — trust the rule.

Remember

• UI shapes the screen, UX shapes the experience, product design shapes the outcome.
• Shortcut: ask "what would prove this right?" A good look, an easy task, or a moved metric.
• Trap: a polished, easy feature that moves nothing is still a product failure.