Talking a Stakeholder Out of a Roadmap Feature Request You Disagree With

A stakeholder asks you, as the product manager, to put a new feature on your roadmap. Having looked at it, you believe the feature should not be built. How would you persuade the stakeholder to drop the request? Walk through how you would evaluate the idea, how you would make your case, and what you would do if they push back. You may anchor the answer in a time you faced this situation. ```hint Problem versus solution Ask yourself what the stakeholder is really trying to achieve, and whether this feature is the only way to achieve it. ``` ### Clarifying Questions - Who is the stakeholder relative to you: a peer in sales or operations, a senior executive, or the owner of a large customer account, and do they control your team's priorities? - Why do you think the feature should not be built: low impact, high cost, a conflict with the product strategy, or a risk such as privacy or reliability? - Has the stakeholder already promised the feature to a customer or to their leadership? - Is there data to size the request (usage, customer feedback, revenue at stake), or would you have to gather it? ### What a Strong Answer Covers - Uncovering the problem and business goal behind the request before judging the proposed feature. - Evaluating the request with evidence (customer need, size of impact, cost, opportunity cost against the current roadmap) rather than opinion. - Making the case in the stakeholder's own terms and giving them another path toward their underlying goal. - Handling continued disagreement: when and how to escalate, and how to keep the relationship intact either way. - Genuine openness to the evidence favoring the feature, and what you would do then. ### Follow-up Questions - The stakeholder is two levels above you and calls the feature non-negotiable. What do you do? - Your analysis shows the feature would earn a small positive return. How do you argue against an idea that is not bad, only weaker than the alternatives? - Months after you talked them out of it, a competitor ships the same feature and it does well. How do you handle that conversation?