Once you've highlighted a new user insight and linked it to a related feature idea, it's up to you to indicate how important it is to the user at hand. Whether the insight represents a feature request, a pain point, or an opportunity uncovered during user research, the significance of this value may vary. But in any event, scoring an insights importance is a helpful way to enable your team to zero in on the features most likely to positively impact users (e.g. by sorting/filtering your features by user impact score).

Suggested guidelines:

For consistency, it's valuable to norm on a set of scoring guidelines with your teammates. You're welcome to adapt the guidelines below which has worked well for team productboard and many productboard customers:

  • +1 importance score: By default, use +1 Nice to have. This adds a point to the linked feature's user impact score. In many cases users reach out with cool ideas that would be nice to have but won't make or break their experience with your product.
  • +2 importance score: For features that could represent a major opportunity or solve a significant painpoint that significantly alters how much value users can get from your product, use +2 Important.
  • +3 importance score: Reserve +3 critical for those features whose absence are likely to lead directly to churn or lost deals.

Occasionally +0 Not important can be useful as well. An example would be if you've polled all the members of your customer advisory board on how much value a feature would generate for them and someone has said the feature would not be particularly valuable at all. In this way you can capture this information without positively influencing the feature's user impact score.

See also: 

Did this answer your question?