Jira Product Discovery is a development collaboration space to help developers communicate new ideas and track their progress towards delivery. Users can record ideas and add data, feedback, and supporting insights, and build consensus and confidence in new product decisions, with integrated product discovery and delivery.
N/A
productboard
Score 6.6 out of 10
N/A
productboard, from the company of the same name in San Francisco, is a product management system designed to help product managers understand what users need, prioritize what to build, and rally everyone around a roadmap.
It was great for handing off projects to Developers and give it into their hands especially by being able to connect to Product Board. Was tricky though sometimes going back and finding things when those backlogs get really lengthy and titles start not helping as much...etc.
The best feature of productboard is organized features, it has a very simple structure and can be read and understood by anyone. If your roadmap is very dynamic and the executive team needs to be on top of it, productboard is the best application out there. But if you have a small product and features do not change very often, then maybe you can look at other alternatives since productboard is expensive.
productboard is my favorite, but that one is more Product oriented where Atlassian Jira Product Discovery seems more Dev focused so it is nice those tools compare. Azure is really nice in the UX and the way it presents the sprints and the stories in an easy manner. Atlassian Jira Product Discovery is great when creating the stories within itself and also works with productboard better than azure does currently.
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.
