TRUSTED BY
Story mapping basics
Webshop Example
Learn to build a standard story map without the extra details.
This story map includes all core elements of product design: main goals (epics), user journey, user personas and the first six releases.
We’ve used MoSCoW prioritization methods and added two user personas.
Open the story map ->
Story map templates
Chat Service Example
Use the template cards in the first column as hints during planning to avoid missing information.
This template will help you build more consistent backlogs and promote shared understanding with developers.
This example also shows you how to design both the backend and the frontend of a product at the same time on the same board.
Open the story map ->
Adding more info
Farming Game Example
This story map represents several solutions that add visuality to a backlog.
First of all, explore what different colors and tags mean and how to tasks such as bugs, ideas and requests under additional releases.
Releases can not only be used for slicing our releases, but also to separate user stories.
Open the story map ->
Story map templates with different mindsets
Journeys
Accommodation website example
This story map was originally designed for introducing the tagging of user stories with emoji icons, and how to filter them with the Search&Filter menu.
The story map demonstrates how a user persona can be identified and assigned to related goals and steps in the user journey.
By adding user journeys to the map you can express a second dimension of user personas, because different personas (with different goals), can have the same journey on the product.
Journeys can be visualized with the search&filter settings.
Open the story map ->
Personas
Accommodation website example
Use our template cards in the first column as hints during planning to avoid missing information.
This template will help you build more consistent backlogs and promote shared understanding with developers.
This example also shows you how to design both the backend and the front end of a product at the same time on the same board.
Open the story map ->
Inspiring public story maps
Coruja Games
We must survive RPG
This story map contains two interesting techniques.
The first is, how to use the different levels on the story map. Putting goals or main requirements on the top level and putting feature groups on the second level (instead of user steps).
The planning team added features but these were too big, and it’s likely they were broken into smaller parts after sending them into an issue tracker.
This is a typical high-level backlog without specifications, releases and detailed user stories but it's perfect for product discovery.
Open the story map ->
Business analysts, product owners, product managers, and teams of all shapes and sizes save time by planning products and enjoy efficient collaboration.
Build a backlog with AI assistance
StoriesOnBoard AI enables a new level of accuracy and speed in software planning and development.
Learn story mapping
with AI
Build an entire story map from just a few details
Understand the essence of the narrative flow, user goals, and user steps
Writing user stories, adoption criteria or release summaries is just a click away with ready-to-use AI recommendations
Save time by writing user stories and more with AI
Craft a product backbone with goals, steps, user stories, and acceptance criteria in seconds
Improve ongoing projects by adding new perspectives and filling the gaps
Add acceptance criteria to each user story, and generate release summaries and announcements with a single click