Feedback Prioritization (Scoring) Tool
Beta now live ➡️ Prioritization module & more 🎯
As it can be quite difficult to decide which feedback to prioritize and work on because it can't always be based just on the number of upvotes - it usually has to be both the user value, market value and the effort that something requires etc. It would be great to have an internal "scoring" tool or system.
This feature would allow POs and PMs to assign certain (internal) scores to the posts, those scores can be from 1-5 and include previously mentioned market value (1-5) and effort (1-5). Effort can go deeper as well, to add for example how research, design and development heavy something is and then get a final score for the effort. This can be done similar to what you have for the users (usage frequency, urgency, importance).
Afterwards it would be easy to sort the posts by both effort required and user value.
I believe that something like this would help a lot with managing user feedback and prioritizing it. And it would certainly be something that would differentiate Featurebase from other similar services.
Log in to comment and vote
Comments20
Bruno H
Nov 1, 2023
PinnedHey!
We just pushed out another update of a more flexible 10-point prioritization system that also allows you to set values by decimal points.
You can enable it from the Prioritization module settings page.
Example:
Oct 27, 2023
Hey everyone!
An initial version of this feature is now live, you can check it out from our latest changelog Feedback Prioritization (Scoring) Tool
Keep in mind that this is the v1 version and we will add more flexibility to it shortly.
I would be incredibly happy if you could try it out and share your initial feedback with us so we can make it even better. 😊
maksumic.anis
Oct 27, 2023
Hi Bruno, I was happy to see the notification about the feature being published. I was wondering where should we leave our feedback after we've done some testing, should we write it here or submit as new posts?
Bruno H
Oct 27, 2023
Hey @maksumic.anis!
You can leave the feedback in this same thread. :)
Teddi
Oct 28, 2023
Some suggestions for improvement
Allowing customization of the range of scores (instead of just 1-5 or exponential)
Allow users to use custom fields and formulas for roadmap prioritization.
This tailors to all companies as one framework is certainly not enough for every company.
Display the prioritization in a table view (see image). This would make it easy for teams to view all posts at a glance and see which post(s) is/are the best to implement based on the result derived after taking Value/Effort (see image)
Allow setting the range of scores to a specific board. Right now, the settings take effect across all boards
Bruno H
Oct 28, 2023
Thanks a lot for the amazing suggestions!
We'll be definitely implementing many things from this list, starting with the custom score ranges.
Ryan Brereton
Oct 31, 2023
Would love to be able to filter posts by Impact/Effort/Unprioritized in the admin section - makes it much easier to talk through the list with the Team :-)
Aug 21, 2023
Thanks a lot for the amazing feedback! :)
This is something we're definitely looking to add in the near future.
maksumic.anis
Aug 21, 2023
That's great to hear! Thanks
Oct 10, 2023
Hey everyone!
We're exploring some ideas in this area now and would love to hear about what the ideal feedback prioritization or scoring framework would look like for you.
We don't want to make the product too complex and would like to strike a nice balance between usability and simplicity.
Please let me know what framework would you prefer and how customizable it should be. For example, RICE, Value/Effort, or an even simpler framework?
Tommy Giesbrecht
Oct 10, 2023
We prefer the Value/Effort framework and group the post by four quadrants like in the matrix above
Bruno H
Oct 10, 2023
Awesome, thanks for clarifying.
This is the approach we've been leaning towards as well.
Cameron Kolick
Oct 10, 2023
We use RICE already internally. Currently, we are connecting to the API, syncing all of the posts, and scoring them in a secondary application that we developed in-house. We would love to see RICE because we already have most of our posts scored, so it would take a lot of effort for us to update all of the scores to a different framework. We would like to consolidate and not have to score in an external system.
Bruno H
Oct 10, 2023
I see, thanks for clarifying.
We're most likely going to support both frameworks in that case.
Cameron Kolick
Oct 10, 2023
I gave this a bit more thought. If you're already leaning toward developing the Value/Effort framework (especially if you've already started it or it is easier for you to bring it to market), we could make that work for us. We would need to create an algorithm to convert our current scores. For the sake of accuracy, could you allow decimals in the 1-5 scale and/or allow it to be 1-10 instead? All of our RICE scores are based on 1-10 range currently.
Bruno H
Oct 10, 2023
Yup, we're gonna allow customizing the range of scores.
Thanks a lot for the clarification, it's much better if we can make one framework amazing, rather than spread our efforts between different types and make the app cluttered.
We're poking the stick at different ideas atm to get a sense of what would work for our target audience.
From the current feedback, we're gonna most likely launch with the Value/Effort framework, and see if there's a need for others after that.
Teddi
Oct 14, 2023
You could probably allow custom fields/formulas for prioritization as different companies have different needs for prioritization.
maksumic.anis
Oct 17, 2023
In our case, the value/effort would be enough at the moment. But, I also believe that the RICE framework might be a good option for organizations dealing with an even bigger amount of user feedback, which will become our case as well, I hope. So having both of those would be perfect, but at the moment I would prioritize the value/effort if I would have to choose between the two.
Also, just a small idea to think about, since both of those frameworks are basically just scoring models, the main differences are in the numbers of factors included (2 vs 4) - what if there was an option to create a custom one? This might be a harder approach to build, but it might be the solution that would have to suit everyone. Basically, add a factor > set the scale from x to y, and the total score would be the average of all the factors. It could go even more advanced if there was option to assign a score for a factor (1-5 for example) which would then affect how much each factor affects the total score. Anyways, its just an idea, and I would still prioritize building the value/effort first.
Bruno H
Oct 17, 2023
Great ideas here, thanks a lot for sharing @maksumic.anis! 😊
Yup, we're gonna most likely launch with the value/effort approach, and build it to be scalable in the back end as we will 100% support other use cases in the future.
Ben Baudat
Oct 15, 2023
I'd start with a value/effort system with a bit of flexibility.
For instance, being able to manage N values for each that can be created with names:
VALUE:
user
market
business
...
EFFORT
research
design
dev
marketing
...
Maybe provide some flexibility as well for the rating where we can decide the max value between 1 and 5. It will be then easy to sum them for both categories and use these values in prioritisation matrix.