How do you say no to a feature request? A no that holds, with a template

Stop saying yes to every feature request. Capacity is fixed, so every yes silently pushes something else off the roadmap, and a soft yes is the slowest no there is. One page on the four questions to ask first, the phrasing that holds, and the words people hear as yes. The print-ready A4 PDF is at the bottom.

Why no matters

• Every yes is a no to something else already on the roadmap.
• A roadmap is a set of bets, not a queue.
• A soft yes is the slowest no.

The 4 questions

• What problem? Not what feature.
• How many users? One loud voice is not many.
• What if we do not? The cost of inaction.
• What do we drop? Capacity is fixed.

Say it

• Not now, plus why: the honest default.
• Name the trade: "this, or the SSO fix".
• Never say "later". Later means never.

Keep the door open

• Log it in a visible parking lot.
• Set a trigger: "if 5 more accounts ask".
• Close the loop: tell them the outcome, whichever way it goes.

The exec ask

• Ask for the goal, then propose the cheapest path to it.
• Show the calendar: what slips, with dates.
• Escalate the choice, not the no.

The no that holds, as a template

Thanks for flagging ⟨the request⟩.
Problem you are solving: ⟨one line⟩.
We are on ⟨the SSO fix⟩ through ⟨Oct 20⟩.
Taking this on now means ⟨X⟩ slips ⟨2 weeks⟩.
Parking it in the backlog, tagged ⟨#billing⟩.
We revisit if ⟨5 more accounts⟩ ask, or
once ⟨X⟩ ships. I will tell you either way.
-- a trade, a trigger, a date. no "later".

Copy it, fill the brackets, send it the same day. The sentence people accept is the one that names what they would be taking away. A no with a visible trade is a decision. A no without one is an opinion.

Gotchas

• A no without data reads as opinion.
• Yes to the loudest is a roadmap by volume.
• No by silence: they hear yes.

The trap: what they hear

Interview phrasing worth memorizing: my job is not to say no, it is to make the trade-off visible so the right person can choose.