Just because the information is provided to decision makers, doesn’t mean that they will make the right choices.
The suggested process to avoid that:
Translate business requirements and user requirements into features, and then prioritize them.
Two key points:
- The best teams develop a features specification, which flows from the business requirements document(s) and the user requirements document(s).
- The best teams prioritize the features based on rankings from three sources: business, users, and IT. The input is typically in the form of numeric ranking; in order of importance from business and users, and in order of doablility from IT.
more at the Tristream Blog