StoriesOnBoard Reviews

Do you work for this company? Learn how we help vendors

(1-3 of 3)

Companies can't remove reviews or game the system. Here's why
February 22, 2021

A tool to feel good

Score 10 out of 10
Vetted Review
Verified User
Review Source
After the company was founded, the software was developed without any feedback from the users. This led to the fact that often only features were implemented and bugs were neglected. There were also many features developed that were not used by the current users. After a reorientation, StoriesOnBoard is very helpful in defining a new, clear MVP and determining the further road map. We also use the tool to illustrate other processes, such as a customer journey and an employee journey. As a startup, everyone who works directly with the software and has gained experience in the exchange with customers is involved in the user stories: CEO, Support, QA and Engineers.
  • 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).
  • Switching the view to a vertical mode (easier to scroll).
  • Better availability of information on user story mapping.
  • Possibility to link to activities and steps from other maps (Context).
As mentioned earlier, we also use StoriesOnBoard to create other processes (customer and employee journey). We use the swim lanes to differentiate between measures, tools and processes and working with them is very easy and understandable for this purpose.

Less easy is the use of context, i.e. when one part of a story map depends on another story map. This cannot be avoided (at least for us) to avoid creating redundancy (and the risk of creating different stages). At appropriate places, we refer to the other map in the title.
February 21, 2021

We love StoriesOnBoard!

Wells Blanchard | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
We use Stories on Board to create story maps for upcoming software (SAAS) development projects. We start with a smaller group meeting, engineering and business leads, map out the high-level "happy path flow", and then add details on sub-cards. After getting a shared understanding and agreement on that, we use the story map to socialize with a broader set of stakeholders, updating with their feedback as we go. While the story map is a living document, we generally will take a screenshot of it and include it in our technical solution documentation and business documentation on our document management system, Confluence. We find StoriesOnBoard to be extremely user-friendly and easy to use, adding cards and sub-cards, adding details on cards as needed, and with the ability to collapse the view to hide the detail cards. While a user experience is almost never linear, we use the "happy path" to map out as best as possible a linear flow.
  • Easy to add, remove, and move cards that represent different parts of the user experience (either external or internal users).
  • Flexible with different views, zooming in, zooming out, hiding detail cards, etc.
  • Can add an infinite number of viewers without having to pay more.
  • It's perfect for our use case, I don't have any real complaints!
Score 10 out of 10
Vetted Review
Verified User
Review Source
My team uses StoriesOnBoard to facilitate communication among internal and external colleagues. Since some functions of development are outsourced, we needed a tool that supported shared understanding. It is also a challenge and rather a lengthy process for a new external colleague to pick up on processes. We find that user story maps can help with that.
  • User role management
  • Jira integration
  • Keyboard shortcuts
  • Filtering by personas
  • Integration for NextGen projects
It's a great end-to-end tool from ideation through prototyping to maintenance. The Jira integration makes backlog management efforless for Jira users.

StoriesOnBoard Scorecard Summary

What is StoriesOnBoard?

StoriesOnBoard is a user story mapping tool for remote agile dev teams, designed to assure that the big picture always stays in focus. By identifying the tasks and features with most value to the user, StoriesOnBoard organises them into releases to help teams build a product users will love with every step in development.

StoriesOnBoard Features

  • Supported: Real-time drag&drop user story mapping for remote teams
  • Supported: Organising the backlog into releases
  • Supported: Reporting, tracking development status
  • Supported: Integration with several issue trackers and tools such as Jira, Azure DevOps, Trello, Slack, Figma
  • Supported: Custom user persona creation for deeper understanding
  • Supported: Various user roles

StoriesOnBoard Screenshots

StoriesOnBoard Workspace DashboardStory map collectionStory map exampleStory card example

StoriesOnBoard Integrations

StoriesOnBoard Competitors

StoriesOnBoard Pricing

More Pricing Information

SaaS Editions Pricing
Pricing DetailsTerms
Basic - billed annually$19per edior
Standard - billed annually$26per edior
Pro - billed annually$45per edior
Enterprise - billed annually$49940+ users

StoriesOnBoard Technical Details

Deployment TypesSaaS
Operating SystemsUnspecified
Mobile ApplicationNo
Supported LanguagesEnglish