StoriesOnBoard

StoriesOnBoard

About TrustRadius Scoring
Score 5.7 out of 100
StoriesOnBoard

Overview

What is StoriesOnBoard?

StoriesOnBoard is a holistic product management tool powered by user feedback. Through collecting user and customer feedback into a single repository and sorting it based on custom rules and collaborating with stakeholders to form actionable feature ideas from them,...
Read more

Recent Reviews

Read all reviews
Return to navigation

Pricing

View all pricing

Basic - billed annually

$19

Cloud
per edior

Standard - billed annually

$26

Cloud
per edior

Pro - billed annually

$45

Cloud
per edior

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://storiesonboard.com/pricing.html

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services
Return to navigation

Product Details

What is StoriesOnBoard?

StoriesOnBoard is a holistic product management tool powered by user feedback. Through collecting user and customer feedback into a single repository and sorting it based on custom rules and collaborating with stakeholders to form actionable feature ideas from them, users can make sure their ideas will be driven by real user needs. Ideas can be validated on a public roadmap and then placed on a user story map to plan releases.

StoriesOnBoard supports the product management process along the followings steps:
  1. Automated customer & user feedback collection via e-mail or any customer facing apps (e.g. Intercom)
  2. Automated feedback sorting based on custom rules
  3. Collaboration in feature idea creation based on customer feedback
  4. Priorization of feature ideas on a kanban board
  5. Validation of feature ideas on a public roadmap
  6. Following up with customers to close the feedback loop
  7. Release planning & scope management on a user story map
StoriesOnBoard features integrations with all most frequently used issue trackers to make the implementation process smooth:
  • Trello
  • Jira
  • GitHub
  • Azure DevOps
  • etc.

StoriesOnBoard Screenshots

Screenshot of StoriesOnBoard Workspace DashboardScreenshot of Story map collectionScreenshot of Story map exampleScreenshot of Story card example

StoriesOnBoard Integrations

StoriesOnBoard Competitors

StoriesOnBoard Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Supported LanguagesEnglish
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

 (8)

Ratings

Reviews

(1-3 of 3)
Companies can't remove reviews or game the system. Here's why
Score 10 out of 10
Vetted Review
Verified User
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.
February 22, 2021

A tool to feel good

Score 10 out of 10
Vetted Review
Verified User
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
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!
Return to navigation