StoriesOnBoard vs. Tabillo

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.

• It's well suited for simple data base applications: simple and fast to put together.
• It's not as well suited if an application requires more complex logics/queries.

• User role management
• Jira integration
• Keyboard shortcuts
• Filtering by personas

• Extremely easy to learn
• Fast to create
• Easy to modify
• Build powerful applications with very little effort
• Absolutely no coding involved

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

• Cannot modify the user interface (it's generated automatically)
• Does not support more advanced concepts

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 only other competitor we looked at was cardboardit.com. Both had solid functionality, but StoriesOnBoard was more user-friendly and quick to learn and use in our opinion.

• Tabillo requires almost no knowledge to use compared to MS Access but cannot build complex applications.
• Tabillo & Salesforce are both simple to learn and use but Tabillo will allow other than sales-centric types of applications to be created (more flexible).

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

• Major improvement within our organization in terms of sharing vital up-to-date information