StoriesOnBoard vs. UserVoice

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

UserVoice is well suited if you field a lot of feedback and ideas from clients. If you are a company who is building your software based on customer feedback, it is important to have a place to store and organize this feedback. I think UserVoice is ideal for a company whose feedback comes into one team but needs to be passed along to another (i.e Support to Product). UserVoice is also great for companies that are growing and growing their product quickly.

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).

• Customer feedback - gives intense insight about what you should build next
• Customer service interface - easy to use, helps users find help without contacting us
• Admin interface - easy and quick to help customers

• Integration for NextGen projects

• Doesn't always catch obvious spam/we have to do a fair amount of blacklisting
• Doesn't have multiple language options
• No online/email tech support available. You have to call if you have an issue.

Incentivized

I just really liked UserVoice.

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.

The day-to-day usability is good. More technical settings require a bit more effort.

Always very responsible and helpful when an issue happened. They eat their own cooking when it comes to using their products.

Have clear goals and owners established before you start using any tool like this. Very important to get accounts and rights setup so that there's no lag time in customer response once things go live. Make sure IT is involved if you plan to use the Single-Sign On (SSO) or any of the access control tools.

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.

I like the ease of integration into web and mobile apps for UserVoice. It's also a comprehensive bug reporting, user feedback, and knowledge base tool.

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.

• Has allowed us to more quickly answer learner questions
• Has allowed us to more easily manage our FAQs page/front facing support information
• Has provided us with a tool to gather daily feedback from our users

Incentivized