A product manager wants to ship a design you believe will hurt users. How do you make your case?

What the interviewer is looking for

• This question tests communicating design decisions. Explains rationale in terms of user and business outcomes, uses evidence, and persuades non-designers without relying on taste alone.
• What to bring out: Frames concerns in user and business terms, brings evidence or proposes a quick test, offers alternatives, and accepts a decision gracefully if overruled.
• Expect a follow-up like: What would you do if the decision still went against you?

Another way it may be asked: Your product manager wants to add a pop-up you think will annoy people. How do you push back?

A structure to follow: STAR, with the weight on Action and Result

1. Step 1

   Situation

   One or two sentences: where, when and what was at stake. Pick a real example you were close to.

2. Step 2

   Task

   What you personally were responsible for. Say "I", not only "we", so the communicating design decisions you showed is visible.

3. Step 3

   Action

   The two or three things you did and why you chose them over the alternatives. This should be about half your answer.

4. Step 4

   Result

   What changed, in your own measure of it, and what you would do differently. Only use numbers you can stand behind.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Describing what the team did without saying what you did.
• Choosing an example with no clear outcome, or one you cannot answer detailed questions about.
• Ending on the action and skipping the result and what you learned.

How to practise it

Write two bullet points for each STAR letter, then say the answer aloud in about two minutes.

Related questions

• Tell me about a time you had to explain a design decision to people who are not designers. How did you make it convincing?
• Walk me through a project in your portfolio, starting with the problem you were solving rather than the screens.
• What are a few things you check to make sure a screen works for people using a screen reader or only a keyboard?
• Tell me about a time you got tough feedback on a design. How did you respond?
• How do you decide on hierarchy, spacing and type on a busy screen? Walk me through a recent example.

Browse all questions