Feature Request Rejection Template

Saying No Is the Most Underrated PM Skill

When Des Traynor, co-founder of Intercom, published "Product Strategy Means Saying No" in 2014, it became one of the most shared product essays of the year. His argument was simple: if you say yes to every feature request, you don't have a product strategy — you have a to-do list written by your loudest customers.

He was right. But knowing you should say no and knowing how to say no are completely different skills. Most PMs are terrible at the second one.

The Cost of Bad Rejections

Here's a number that should keep you up at night: according to a 2023 Zendesk Customer Experience Trends Report, 61% of customers will switch to a competitor after just one bad experience. A poorly handled feature rejection is exactly that kind of experience — especially for customers who took the time to submit a thoughtful request.

The typical rejection sounds like this: "Thanks for the feedback! We'll add it to our backlog." Everyone knows that backlog is where feature requests go to die. The customer feels dismissed. The sales rep who forwarded it feels unsupported. Trust erodes.

On the internal side, the damage is different but just as real. When PMs can't articulate why they're saying no, sales teams start going around them directly to engineering. Customer success teams promise features they can't deliver. The organization loses confidence in product's judgment. A good rejection, on the other hand, actually builds trust. It shows you understand the underlying need, have thought about it seriously, and have a coherent reason for your prioritization. Stripe is famous for this — their PMs respond to feature requests with detailed explanations of their current priorities and how the request fits (or doesn't) into their strategic direction.

How This Prompt Helps

This prompt generates professional rejection templates for different scenarios — saying no to a customer, to a sales team, to an executive, to a partner. Each template acknowledges the request, explains the reasoning, and offers an alternative path forward. It also includes objection handling for the most common pushback you'll receive.

The goal isn't to shut people down. It's to say no in a way that maintains the relationship and reinforces trust in your product judgment.

When to Reach for This

• A key customer has requested a feature that doesn't align with your roadmap and you need to respond without damaging the relationship
• Sales is pushing hard for a one-off customization and you need to explain why it's a bad precedent
• You're doing a quarterly roadmap review and need to communicate what's not making the cut and why
• An executive has a pet feature idea that doesn't make strategic sense and you need a diplomatic response
• You want to establish a consistent, professional template for handling feature rejections across your team

What Good Looks Like

A strong rejection acknowledges the underlying need (not just the specific feature), explains the prioritization logic transparently, offers an alternative or workaround where possible, and leaves the door open for future re-evaluation. It should never feel dismissive. The best rejections make the requester feel heard and respected, even when the answer is no. If the person responds with "I appreciate the thoughtful explanation," you've done it right.

Sources

• Customer Experience Trends Report 2023 — Zendesk
• Product Strategy Means Saying No — Intercom (Des Traynor)
• How Stripe Says No — The Pragmatic Engineer