The hardest sentence in product management isn't "yes" or "no". It's what comes after. A quick no protects today's roadmap but costs tomorrow's trust.
The request isn't the problem
When a stakeholder asks for a feature, they're proposing a solution to a problem they see. Reject the solution without understanding the problem, and they'll come back with another solution to the same problem.
Three questions before you decline
- What problem is this request trying to solve?
- Who is affected, and how often does it happen?
- What's the smallest thing that could ease it now?
The conversation often moves from "no" to "not this way", and that makes a big difference to the relationship.