How do you say no to a stakeholder request?
What the interviewer wants to hear
- Listen and understand the need behind the request
- Explain the decision using goals, data and trade-offs
- Offer alternatives or a later time
- Keep the relationship and stay transparent
Model answer
Saying no is a normal part of the job, but how I say it matters. First I listen and make sure I really understand the need, because sometimes the request is a solution to a problem that can be solved another way. Then I compare it with our current goals and priorities. If it does not fit, I explain why clearly, using our goals, the evidence and what we would have to give up to do it. I try to offer something: a simpler alternative, a workaround, or a time when we will review it again. I keep the request in our backlog with notes so the person knows it was taken seriously. Being consistent and transparent with everyone makes it much easier for people to accept a no.
Can you answer it under time pressure?
Take a timed medium round and get scored on every answer.
More medium Product Manager questions
- How would you define success metrics for a new feature?
- How do you run customer discovery for a new problem area?
- Tell me about a feature that did not perform as expected. What did you do?
- How do you write a product spec or PRD that engineers find useful?
- Leadership wants to change your product's pricing. How would you approach it?
- Walk me through how you plan a major product launch.
- Your A/B test finished and the result is not statistically significant. What do you do next?
- How would you set OKRs for your product team for next quarter?
- How would you tell whether a new product has product-market fit?