Marcus Andrey Study
Ler em português Library

UX Foundations · Step 1 · 4 min read

Who does what on a product team

UX design is a team sport. The roles you'll work with (product manager, engineers, researchers, content designers, design systems, QA, data), the product trio at the centre, what the usual team ratios really mean, and how to agree who decides what.

No designer ships a product alone. A good experience comes from a team that agrees on the problem, respects each other's expertise and knows who decides what. Knowing the roles around you, what each one worries about and when to bring them in, is one of the most practical UX skills there is, and one that design courses often skip.

What you'll be able to do after reading:

  • Name the roles on a typical product team and what each one owns
  • Explain the product trio and why it matters for designers
  • Read team ratios without treating them as rules
  • Agree who is responsible for what, with a simple table

1. The roles you'll meet

ValueProduct manager

What to build and why it matters.

Priorities, business goals
UsableProduct designer

How it works and feels for people.

Flows, screens, states
FeasibleEngineers

How to build it well.

Architecture, performance, quality
EvidenceUX researcher

What we know about people.

Interviews, tests, analysis
WordsContent designer

What it says, and how.

Labels, messages, tone
SystemDesign systems

Shared components and rules.

Library, tokens, docs
Roles you will work with. The first three form the product trio. Diagram: Marcus Andrey, CC BY 4.0.

Not every team has every role. In a small company one person may be designer, researcher and writer; in a large one each role may be a whole team.


2. The product trio

Teresa Torres describes the core of a product team as a trio: "A product trio is typically comprised of a product manager, a designer, and a software engineer" (Product Talk, May 2021). The three decide together what to build, bringing three views: is it valuable (product), is it usable (design), is it feasible (engineering). NN/g describes the designer's part in it as bringing user evidence into every decision (NN/g, The Product Triad: Design's Role, Jul 2025).

What this means for you: don't wait to be handed requirements. Join the conversations where problems are chosen.


3. What the ratios really say

In NN/g's 2020 survey, the most typical ratio was 1 researcher to 5 designers to 50 developers; an earlier survey by Jeff Sauro found 1:5:100. NN/g also found that the ratio itself didn't predict the business impact of UX (NN/g, UX-Developer Ratio, Nov 2020). These are survey answers from people who chose to respond, not a target. The useful lesson: designers are usually few, so how you work with others matters more than how much you produce alone.


4. Who decides what

Teams argue less when they agree upfront who does what. NN/g suggests a RACI table for UX work: who is Responsible (does it), Accountable (decides), Consulted (gives input), Informed (kept up to date) (NN/g, Setting UX Roles and Responsibilities, Jun 2022).

Decision Product Design Engineering Research
Which problem to solve next A C C C
How the flow works C A C C
Whether it can be built this sprint C C A I
What we learned from users I C I A

Fill it in with your team; the exact letters matter less than the conversation.


5. Common mistakes

  • Designing in isolation and "handing over" a finished design.
  • Bringing engineers in only after the design is approved.
  • Treating the product manager as the enemy instead of a partner.
  • Saying yes to every request instead of asking which problem it solves.

6. Vocabulary

Term Meaning
Product manager (PM) Owns what the team builds and why: value for users and the business
Product designer Owns how it works and feels for people, from flows to visual detail
UX researcher Plans and runs research so decisions are based on evidence
Content designer / UX writer Owns the words: labels, messages, help, tone
Product trio PM, designer and engineer deciding together what to build
RACI Responsible, Accountable, Consulted, Informed: who does what in a decision

7. Try it (no tools needed)

  1. Draw the people involved in one product you know (at work, or a public app you can imagine).
  2. For each role, write one thing they worry about most.
  3. Fill in the RACI table above for one real decision.

Reflection questions: Which role do you understand least? What could you ask them this week to understand their worries?


8. If you already practise

  • Invite an engineer to your next research session or usability test; it changes the conversation afterwards.
  • If you're the only designer, write down which decisions you're accountable for and agree it with your PM.
  • Marty Cagan's Inspired explains the product team from the product side; worth reading to understand your PM (Inspired, 2nd edition, Wiley).

Checklist

Learn more

Books, courses and videos to go deeper

Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

What UX design is (and isn't) · The design process · Users, tasks and context · Design critique · DACI · Guiding designers through AI adoption

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close