How do you say no to feature ideas or requests?

As a product manager, saying “no” to feature requests is not about outright rejection but about ensuring alignment with the product’s vision, strategy, and priorities. Here’s how I approach it:

Start by Understanding the Request

• • I ask clarifying questions to understand the motivation behind the request.
    Example questions: What user problem does this solve? Who is the target audience? What metric does this improve?
  • This step ensures I show genuine interest and gather context.

Evaluate the Request Against Priorities

• • I assess the request using objective frameworks like RICE (Reach, Impact, Confidence, Effort) or cost-benefit analysis to compare it against current priorities.
  • If the idea doesn’t align with the product’s strategic goals, I explain why:
    For example: “This is a great idea, but our current focus is improving retention metrics. This feature impacts acquisition, so we’ll revisit it later.”

Leverage Data to Support the Decision

• • For stakeholders at any level, I use data to explain my decision. Data ensures the reasoning is objective and depersonalized:
    Example: “Our data shows onboarding conversion rates are already above 80%, and this idea focuses on optimizing onboarding further. Right now, we’re prioritizing features to boost daily active users.”

Explore Alternatives and Acknowledge Contributions

• • Instead of outright rejecting the idea, I consider alternative solutions or paths:
    Example: “This is an interesting way to solve the problem. Could we explore a simpler version as an MVP or tweak an existing feature to address this?”
  • I always thank the person for their input and emphasize the importance of their contributions.

Communicate Transparently and Empathetically

• • I avoid saying “no” outright. Instead, I reframe it as a prioritization decision:
    Example: “This idea has potential, but given our current priorities, we’ll need to delay it for now. We’ll revisit it in the next planning cycle.”
  • Transparency builds trust and shows respect for their ideas.

Document and Revisit

• • I ensure the idea is captured in a backlog for future consideration. This demonstrates respect for the suggestion and allows us to revisit it when priorities shift.

Coach Junior or Peer Stakeholders

• • If the idea comes from colleagues or juniors, I encourage them to provide supporting data, metrics, or research. This empowers them to critically evaluate ideas and fosters a collaborative culture.

Key Takeaway for PM Interviews

By demonstrating a structured approach to declining feature requests, you showcase your ability to balance user needs, business goals, and team collaboration. This not only highlights your leadership but also your decision-making and stakeholder management skills.

Practice Questions