Q:How do I say no to feature requests?

Saying no is a core part of the PM job, and Lenny Rachitsky recommends a three-step process: listen and ask questions, form your own point of view, then respond constructively³. Lenny's post suggests asking at least three questions before reacting, such as what your manager sees that you don't³. Your answer should be a specific, reasoned response rather than a bare refusal³.

01Listen and weigh the request

• Lenny advises avoiding a quick yes or no, especially when an idea seems poor, and getting curious first³.
• Form your own view by weighing downside, upside, timing, and strategic fit³.
• Marty Cagan says your job is to deliver valuable, usable and feasible products, and a feature-request list works against that by pushing through features users don't need⁵.

02Choose a response path

• Rachitsky offers five responses, from "yes, but here's what needs to change" to "no, because it's a bad idea for reasons XYZ"³.
• A middle option is "no, but how about we do XYZ instead, which achieves a similar outcome," since your manager may have spotted a real opportunity without the best solution³.
• When declining, lead with unbiased facts and evidence rather than opinions³.

03Frame the trade-off

• Tara Seshan, as shared by Rachitsky, recommends repeating your public priority list so new requests are judged against it⁶.
• She also advises framing trade-offs around company goals and spelling out what would be cut, rather than vague replies like "we're thin on resources"⁶.
• Ken Norton's approach, as quoted by Rachitsky, is to review the roadmap and strategy together so your manager sees why current work stays the priority³.