Every product owner has faced the dilemma: a customer comes forward with a passionate request for a feature that isn’t on your radar. Sometimes it’s a perfect fit, but often, it’s something that serves a niche use case or distracts from your product’s core focus. In a past episode, Katie Keith, James Kemp, and guest Bryce Adams went deep on the art and impact of saying “no” to feature requests without losing goodwill.
Why Saying No Is So Hard
As developers and product builders, we know the thrill (and the dopamine hit) of shipping something new. Bryce Adams describes this well: “We’re very tempted by new shiny things…sometimes features that we won’t even use ourselves.” The itch to build, coupled with direct customer requests, can lead to feature creep and a loss of product focus.
Katie Keith notes the risk of being “too close” to customer support: “Founders doing customer support are too close…they just want to help that one customer.” This is where the danger of saying yes to everything creeps in.
Our sponsors keep the lights on.
Take a moment to check them out.
Since 2005, Automattic has built tools for the open web including WordPress.com, WooCommerce, and Jetpack that are used by millions of people to create, sell, and publish online. They believe in ownership, flexibility, and open source and we’re grateful for their support. Learn more at automattic.com.
InMotion Hosting brings over 25 years of experience, NVMe-powered speed, and 99.99% uptime to every plan they offer. When you need help, you get a real human, not a bot, and they’ll migrate your site for free. We’re happy to have them in our corner supporting the conversations we have here at Open Channels FM. Find your plan at inmotionhosting.com
Omnisend just dropped SMS pricing to $0.007, and their migration team moves your automations, templates and contacts in five days, free. That means you could be saving up to 35% in less than a week. We’re glad to have them supporting the show and the community we’re building around it. Use the code OpenChannels and get 30% off your first 3 months of any paid plan.
How Product Teams Politely Decline
Rather than a blunt “no,” the guests share several positive strategies:
Offer Honest, Transparent Explanations
Bryce stresses the need to be honest: “If it’s out of the question, I’ll sometimes just say straight away, ‘This is not going to happen. If you need this, you should use something else,’” but he always tries to provide alternatives or explain the reasoning: “We have 3,000+ other customers to think about…that’s why.”
Katie adds that sharing numbers can help: “We have 200 items on the list. You are the second person to request this. The top item has 56 votes…so we have to do that first.”
Suggest Alternatives or Workarounds
If your product can’t (or shouldn’t) do what’s being requested, try to help another way. Sometimes this is recommending another product, plugin, or even a customization service. As Katie shares, “We’ll often recommend another product…or ask if they want a quote for a customization.”
Use Data to Prioritize
Both teams use private spreadsheets or issue trackers to log and quantify requests by frequency, impact, and development difficulty. This helps prioritize and justify their choices to users.
Create Add-Ons for Major Requests
If a feature is frequently requested but not core to the main product, it might make sense as an add-on or integration. This way, the “core” product stays lean, and those who need specialized features have an option.
The Benefits of Saying No (the Right Way)
At the end of the day, saying no preserves your product’s vision and maintains sustainable development. Most importantly, as Bryce points out, “If someone doesn’t understand at that point, they’re never going to; they’ve made their mind up.” By being transparent and helpful, you can retain goodwill, and sometimes even inspire customer respect for your leadership and focus.
Next time you’re faced with a tricky feature request, remember: saying no honestly, helpfully, and with context is a “yes” to your product’s long-term health—and often, your user’s best interests too.
