Tactfully rejecting feature requests

We’ve all seen this: a backlog composed of at least 2 to 3 months of commitments, and a seemingly endless supply of issues and requests coming in from internal and external stakeholders.

You then receive one or more “urgent” or “high priority” issues from your CEO, Sales, or Leadership team, asking for you to stretch your capacity one more time to take on some new item of work.

How can product professionals respond to the ebb and flow of incoming work items and feature requests? We know that the key is to say “no”, but how do we do this in a compelling yet respectful way?

Offered below is a few steps you can take to quickly understand whether to accept or reject incoming requests, as well as a method for communicating a “Positive No” that is both respectful and solution-oriented.

Collections featuring this content