Move the argument off opinions and onto the problem statement, because most design disagreements are actually unresolved disagreements about the user or the constraint. Restate what you each think the user is trying to do, agree the success criteria, then let the designer own the solution space. If it is still split and expensive to get wrong, test both with a handful of users.
Why interviewers ask this
Interviewers are assessing whether you respect craft boundaries. The product manager owns the problem and the outcome, the designer owns the solution, and candidates who override design decisions on taste are a known source of friction. They also listen for whether you add context rather than authority, and whether you have a cheap tiebreak that does not resolve by seniority.
How to structure your answer
- Reframe the disagreement as a problem definition gap.
- Write down the user, the job, and the constraints together.
- Defer on solution space; own the problem and the outcome.
- Break a genuine tie with a cheap test rather than seniority.
Example answer
Almost every design disagreement I have had turned out to be a disagreement about the problem, not the pixels. So I stop arguing about the solution and we both write down who the user is, what they are trying to do, and what constraint we are under. Half the time the gap is right there in front of us. If we still disagree after that, I defer, because the solution space is the designer's job and mine is the problem and the outcome. The exception is when I have information they do not, like a constraint from sales or a technical limit, and then my job is giving them that context rather than overruling them. If it is genuinely even and expensive to get wrong, we put both in front of five users, which takes two days and settles it with something other than seniority. That has changed my mind at least as often as theirs.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- What do you do if the designer's solution misses a technical constraint?
- How do you handle it when engineering also has a strong opinion?
- Tell me about a time you were wrong about a design decision.
Related product manager questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions