This User Story Map Examples page is perfect to get inspired or to learn new story mapping tricks and techniques. Some of the examples here are made-up, but they still give a good overview of the StoriesOnBoard product. Of course, we’ve included some real-life examples too. The main purpose of this page is not to hand over ready-to-bake story map templates, but to introduce different mindsets behind the core story mapping method.
User story mapping is an agile product design method. Design with user story mapping is one of the best ways to create a user-centered product. The process of product design should always begins with understanding the problem and the user's goals.
If you are new to user story mapping, read more about the process here.
These story maps have been made up by our team and represent how a typical user might make use of story mapping. You might find that these examples may lack detail ... this is deliberate. It’s so we can encapsulate whole user journeys. These roughly finished projects are good starting points. We hope you can relate to them at least a litte, and maybe even add your own details, personas or journeys.
Here, you can learn how to build a standard story map. Like we said, there’s no detail like you’d find in a live project, but it contains all the core elements of product design: main goals (epics), user journey, user personas...etc.etc. We created the first six releases, which, we feel represents a well-sliced release strategy. We’ve used MoSCoW prioritization methods and applied two user personas. If you want to be inspired about specifying personas, start by opening the persona tab. You can then follow the persona marks to discover the two main users in this journey. This story map is also integrated to Trello, so open the connected board to see how to push cards to execution. Open Story Map
This story map represents several solutions that add visuality to a backlog. First of all, explore what the different colours mean by a right-clicking on a card. There are tons of possibilities opened up by using card colors (labels). They can express statuses, annotations, task types...etc. etc. Although release details let you add a sophisticated specification to each release, you can highlight the goal by adding it to the actual release name, or by adding an annotation card on the first column. This story map is a great example of how to group unprioritized tasks such as bugs, ideas and requests under additional releases. Releases are not just for slicing the backlog, they could be a container for user stories. Open Story Map
In this example, you can discover a template card in the first column. You’ll avoid missing information during planning by using templates for the user story details. Make up your own scheme for specifications and roll out this structure across all cards. A consistent backlog builds shared understanding and improves developer efficiency. There is another feature on this story map too. You can design both the backend and the frontend of a product at the same time on the same board. Just create different personas (administrator, user), and put frontend and backend activities next to each other. This solution provides you with a high-level overview of the product. Sync frontend and backend stories during the release planning and avoid useless developments. Open Story Map
In this group, we share story maps with different solutions for different needs. The core structure of this is the same, but some parts could be very different from the above-introduced examples. Go through these story maps and collect the best fitting solutions for your project needs.
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 Story Map
This story map is almost the same as the previous one. The story map's backbone and the user stories are the same. We added the same user personas. This story map template can be interesting because of two things. The first useful solution is - when using tags - creating “legend cards” in the first column, and add some explanation to the tags and mark signs. The second opportunity is the use of emoji icons as a tag. It opens unlimited opportunities to add more visuality and the possibility to filter the backlog by a selected tag. Use these tags when you ran out of card colors or would add a second or third dimension of labelling eg: label by teams, priority, risk level etc. Open Story Map
It's always inspiring and interesting to browse someone else’s board to explore different mindsets. They might not follow the standard user story mapping rules but they could add hints for better usage of the method.
This story map contains two interesting methods. 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 Story Map