productboard vs. StoriesOnBoard

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.

Incentivized

It's a great end-to-end tool from ideation through prototyping to maintenance. The Jira integration makes backlog management efforless for Jira users.

• Flexibility - organize your products and features in any way you like
• Input - give your teams a way to make suggestions and provide feedback
• Integrations

Incentivized

• Individualization of maps, annotations and colors.
• Clear display depending on the situation (hiding stories).
• Handling of the cards in case of changes.
• The possibility to change content directly in the overview (title, annotation, color).

• 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

Incentivized

• Integration for NextGen projects

StoriesOnBoard works really well; all features are well thought through. It could look a bit fresher, although the new updated dashboard is already much better than it was.

Easy to contact right through their Intercom app and incredibly fast to respond.

Incentivized

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.

Incentivized

Miro: The handling in Miro was not comfortable enough. Easy Agile User Story Maps for Jira: The integration with Jira was a great idea, but the handling on the map was not good. Also, there were only 2 layers, which made it very difficult to define the cards.

• Helps to save us a lot of time collecting feedback.
• Increased efficiency.
• Product prioritization can be done in a faster and more robust way.

Incentivized

• StoriesOnBoard (and story mapping in general) creates a low-cost visual method of aligning on high-level business and technical requirements early in a project and provides an ongoing reference as the project progresses. Having this alignment is critical for the later stages of the project.