Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 36 ยท Getting Started

UX, UI and Related Roles

Understand the difference between UX and UI design, and how researchers, content designers, product designers and developers fit together on a product team.

"UX" and "UI" are often written together as if they were one thing. They overlap, but they are not the same. Knowing the difference helps you read job ads, talk to teammates, and decide which skills to learn first.

UX versus UI

UI (user interface) design is about the surface people see and touch: layout, typography, color, icons, buttons, spacing, motion. UX design is about the whole experience: whether the right thing exists, whether people can find it, whether the steps make sense, and whether the result is good.

A simple analogy is a house. The architect decides how many rooms there are, how they connect and where the doors go. That is closer to UX. The interior designer chooses paint, furniture and lighting. That is closer to UI. A beautiful kitchen on the wrong floor, far from the dining room, is still an awkward house.

Question Mostly UX Mostly UI
Do users need this feature at all? Yes
Where does it live in the product? Yes
Is the button clear and easy to hit? Both Both
What color and shape is the button? Yes
Does the flow match how people think? Yes

In small teams one person often does both, and the best UI work depends on solid UX thinking. Treat them as two lenses on the same design.

The wider cast

A product is rarely built by one designer. These roles often work together, and the names vary between companies.

  • UX researcher: plans and runs studies, such as interviews and usability tests, and turns findings into insight.
  • Interaction designer: focuses on how the interface responds: states, transitions, gestures, feedback.
  • Information architect: structures content and navigation so people can find things.
  • Content designer / UX writer: writes labels, instructions and error messages, and shapes the voice of the product.
  • Visual / UI designer: creates the look, design system and assets.
  • Product designer: a broad role that covers UX and UI for a product, often from research to shipped result.
  • Product manager: decides what the product should achieve and in what order.
  • Developer / engineer: builds the product and tells the team what is feasible.
  • Accessibility specialist: makes sure the product works for people with disabilities.

Who works on a product

Researcher Finds what people need
UX designer Shapes flows and structure
1 / 2

Where the lines blur

Titles are not standardized. At a start-up, "product designer" may mean one person who interviews customers, draws screens, writes microcopy and even edits front-end code. At a large company the same work is split across five specialists. When you read a job description, look at the actual duties rather than the title.

A practical career tip: learn the core of UX first (research, structure, flows, testing), then add depth in whichever area you enjoy, such as visual design, writing or research.

Collaboration is a skill

UX designers spend a lot of time communicating. They explain why a decision was made, show evidence, and listen to constraints. A developer may say a design is expensive to build, and the designer then looks for a version that keeps the goal at lower cost. A product manager may need a date, and the designer explains what can be tested before it.

Some habits that make collaboration smoother:

  • Share work early, while it is still cheap to change.
  • Explain decisions by pointing to user evidence, not personal taste.
  • Ask developers about limits and platform conventions.
  • Write down agreements so nobody works from a different version.

A stand-in: routing questions to roles

To make the split concrete, this stand-in maps typical questions to the role that usually owns the answer. It is a teaching toy, not a real tool, and real teams share ownership.

JS Who owns this question? (stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The last line returns the fallback on purpose: many questions have no single owner, which is why teams meet and decide together.

Choosing your path

If you like talking to people and finding patterns, research may suit you. If you enjoy structure and logic, look at information architecture and interaction design. If you love craft and detail, UI and visual design. If you like all of it and working end to end, product design is a good target. You do not have to decide today; the rest of the course gives you a taste of each area.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which task is closest to UX rather than UI?

    Deciding what steps exist and in what order is about the experience and flow, which is UX.
  2. 2. What does a content designer or UX writer mainly work on?

    Words are part of the interface. Content designers make them clear and consistent.
  3. 3. Why can job titles like "product designer" mean different things?

    At small companies one person covers many areas; at big ones the work is split.
  4. 4. Which habit helps designers and developers work well together?

    Early sharing keeps changes cheap and builds shared understanding.

Summary

  • UX is the whole experience; UI is the visible surface. They are two lenses on the same work.
  • Teams include researchers, interaction designers, content designers, UI designers, product managers and developers.
  • Titles vary; judge a role by its duties.
  • Collaboration and clear explanation are core UX skills.

Next: The UX Design Process