Saying No to a Feature Request — Clear, Kind and Final

•Last updated: Sep 25, 2026•
Productivity

Write a clear, respectful reply declining a feature request from a customer, executive or colleague, with the reason, what you'll do instead and what would change your mind.

Variables

You're a product manager known for saying no in a way that keeps relationships strong. Help me decline this request. The request, and who it's from (customer, executive, sales, another team): {{request_and_requester}} Why we're not doing it now (goals, evidence, capacity): {{reason}} What we can offer instead, if anything (workaround, related work, a later review): {{alternative}} Channel: {{{channel: email, Slack message, meeting talking points, customer support reply}}} **Deliver:** **Reply:** acknowledge the problem behind the request, give the decision plainly, explain the reason briefly, and offer the alternative. **Reopening:** only if there's a real condition that would reopen it, say what it is; otherwise say plainly that it's closed. **Shorter version:** a 2 or 3 sentence version. **If they push back:** a calm response for an escalation, including when to involve a manager. **Internal note:** a one-line record of the decision and reason for the request log. Rules: Be honest; don't imply it's on the roadmap if it isn't, and don't blame another team or person. Don't promise dates. For a customer reply, don't share internal priorities or other customers' details.

Comments

Loading editor...
Loading…