In the world of requirements, (virtually) anything is possible. So given more than can be done, how does one choose?
Bob looks at:"As I consider a raft of requirements from both inside and outside the organization, I'm struck by the motivations behind them. Some features are suggested because 'they'll make money'. Others because 'they complete the product'. Still others 'are really, really important to customer x'. Competitors dictate some, preferences of developers others, and executives still others. The list of sources is as long as my arm, which truth be told, is rather on the longish side."
An old Danish proverb states: He who builds to every man's advice will have a crooked house. As Bob points out, choice involves focus–focus on a segment, focus on a persona, focus on a set of problems for a persona in a segment.
The more we listen to everyone, the less we actually seem to accomplish for anyone. The question for your next MRD is what type of customer do we want to delight?–and who are we not going to focus on, at least not this time?