productboard- Insights into your Product Insights
April 30, 2024
productboard- Insights into your Product Insights
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with productboard
productboard is used in our organisation to manage product roadmaps, suggestions for product insights and to spec out features and enhancements for our products.
It provides a platform for the R&D team to not only capture suggestions but visualise what that would look like in terms of development hours.
I am an end user for suggestions and insights but have some visibility on the wider product when assisting with the R&D team
It provides a platform for the R&D team to not only capture suggestions but visualise what that would look like in terms of development hours.
I am an end user for suggestions and insights but have some visibility on the wider product when assisting with the R&D team
- Capturing Insights
- Focus Bubbles for Insight hit markers
- Grouping/Tagging suggestions together
- The interface could be improved
- Input field options could be less restrictive to the capture of data
- Better notifications / updates on where insights have got to
- Solidified our Product Roadmap processes
- Project labour time has become quantified not theorised
- Quantified reflection on use case numbers
I have previously used Aha another product road mapping/ insights driven software.
Aha had great features for the userbase of my previous products. They were allowed to create their own suggestions for the products and other users could then like or dislike the suggestion. This created a real reflection on need for product enhancements.
productboard handles this slightly differently. Each user creates their own suggestions and doesn't necessarily have visibility on other users suggestions. The product/ R&D team can then tag suggestions together into the same overall suggestion. This requires more input from product/R&D with productboard.
I would however, suggest that productboard is better than Aha. Aha is great for an external user point of view; however, there may be case for users to not have visibility on wider user requirements. productboard keeps more of this element hidden and would perhaps stir up less negative correlation to seeing a system requirement/suggest having had a lot of traffic and no action, compared to a more closed system that would individually update each user on the enhancement progress.
Aha had great features for the userbase of my previous products. They were allowed to create their own suggestions for the products and other users could then like or dislike the suggestion. This created a real reflection on need for product enhancements.
productboard handles this slightly differently. Each user creates their own suggestions and doesn't necessarily have visibility on other users suggestions. The product/ R&D team can then tag suggestions together into the same overall suggestion. This requires more input from product/R&D with productboard.
I would however, suggest that productboard is better than Aha. Aha is great for an external user point of view; however, there may be case for users to not have visibility on wider user requirements. productboard keeps more of this element hidden and would perhaps stir up less negative correlation to seeing a system requirement/suggest having had a lot of traffic and no action, compared to a more closed system that would individually update each user on the enhancement progress.
Do you think productboard delivers good value for the price?
Not sure
Are you happy with productboard's feature set?
Yes
Did productboard live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of productboard go as expected?
I wasn't involved with the implementation phase
Would you buy productboard again?
Yes