How do you say no to a stakeholder's feature request?
Model answer
Model answerSaying no well is one of the most important PM skills. The key is never saying no to the request — say no to the priority. 'I can't prioritize this now because we're committed to X, which has higher expected impact based on Y criteria. Here's when I could revisit it.' You're not dismissing them — you're making the tradeoff explicit. Always give a 'when', not just a 'not now'. And if you're wrong about the priority, this conversation is exactly how you find out.
Framework · Stakeholder Alignment
- LListen for the real need
The feature request is often a symptom — find the underlying goal before responding - EExplain your current priority
Make the tradeoff explicit: 'if we do this, we delay X' — bring them into the decision - AAcknowledge their goal
I understand why this matters for your team' — validate before declining - DDefine a when
Not now' isn't no. Give a timeframe or a condition under which it could be revisited
Related questions
- What is product-market fit and how would you know if you have it?
- You have 3 features requested by customers and only 1 sprint. How do you decide?
- How would you communicate a feature delay to stakeholders?
- How do you handle a situation where engineering says a feature is impossible?
- How would you explain your product roadmap to an engineer who thinks all roadmaps are a waste of time?