How to Answer "Describe a Time You Said No to a Feature Request"

Saying no is one of the hardest and most important skills for a product manager. This question tests whether you can resist scope creep, maintain product vision, and handle the interpersonal friction that comes with declining requests from passionate stakeholders.

Interviewers look for PMs who say no with data and empathy rather than ego or stubbornness. Your answer should demonstrate strategic reasoning, diplomatic communication, and a constructive outcome.

What Interviewers Are Really Assessing

• Product vision clarity: Do you have a coherent view of what the product should and shouldn't be?
• Courage to pushback: Can you resist pressure from loud voices, including executives and large customers?
• Data-driven reasoning: Is your "no" grounded in evidence, not personal preference?
• Stakeholder empathy: Do you validate the requester's underlying need even while declining the specific ask?
• Alternative thinking: Do you offer a different path to address the underlying problem?

How to Structure Your Answer

Walk through: (1) who requested what and why it seemed reasonable, (2) your analysis of why it didn't fit, (3) how you communicated the decision, and (4) what happened as a result. Show respect for the requester throughout.

Sample Answers by Career Level

Entry-Level Example

Situation: Sales team pushing for a custom dashboard feature to close a prospect. Answer: "Our top sales rep asked for a custom analytics dashboard for a prospect willing to sign a $50K annual contract. I analyzed our existing customer base and found that only 3 of 200 customers had ever requested custom dashboards. Building it would take six engineering weeks—time allocated to our onboarding redesign that would impact all new users. I met with the sales rep, validated that the prospect's underlying need was data visibility, and proposed we instead build a CSV export feature in two days that would serve both this prospect and 40 other customers who had requested data export. The sales rep agreed, the prospect signed with the export feature, and we stayed on track with our onboarding work that improved activation by 15%."

Mid-Career Example

Situation: CEO requesting a social sharing feature based on a competitor's launch. Answer: "Our CEO saw a competitor launch social sharing and wanted us to build it within the quarter. I spent a week analyzing the data: our users were B2B professionals who used our tool during work hours, and our existing share-via-email feature had only 4% adoption. I surveyed 50 active users and found zero interest in social sharing—they actually valued the privacy of our platform. I presented these findings to the CEO alongside competitor usage data showing their social feature had low engagement. I reframed the conversation around what our users did want—better team collaboration—and proposed investing in shared workspaces instead. The CEO agreed, we built team workspaces, and it became our highest-adopted feature with 62% of accounts using it within three months."

Senior-Level Example

Situation: Board member pushing for an AI feature to match market trends. Answer: "A board member pressured us to add a generative AI feature after seeing several portfolio companies do so. Rather than dismissing it or blindly complying, I conducted a two-week opportunity assessment. I found that while AI was relevant to our space, the specific feature suggested would require six months of development and didn't align with our users' top three pain points. I presented an alternative: a focused AI-assisted recommendation engine that addressed our biggest churn driver—users struggling to find relevant content. I showed that this targeted application would deliver ROI within one quarter versus the speculative six-month bet. The board approved the focused approach. We launched the recommendation engine in eight weeks, and it reduced content discovery time by 40%, directly improving our retention metrics."

Common Mistakes to Avoid

• Being dismissive: Saying "that's a bad idea" rather than explaining your reasoning with data alienates stakeholders and makes you look closed-minded.
• No alternative offered: A bare "no" is incomplete. Always propose an alternative path that addresses the underlying need.
• Making it personal: Focus on strategic fit and data, never on why the requester is wrong. Frame disagreements as collaborative problem-solving.

Practice This Question

Ready to practice your answer with real-time AI feedback? Try Revarta's interview practice to get personalized coaching on your delivery, structure, and content.