User story mapping organises the backlog along the path a person takes. At the top sit the activities (the backbone), below them the steps of each activity and, under each step, the stories, from the most essential to the least. A horizontal line slices the releases: the first story of each step forms the walking skeleton, the smallest version that works from start to finish.
How to use
- Write the product or the user’s goal at the root.
- Add the activities, in the order the person goes through them, and the steps of each one.
- Under each step, list the stories from the most essential to the least.
- Choose 2 or 3 releases and see the suggested slices, starting with the walking skeleton.
- Export the map as PNG or the sliced backlog as CSV, or take release 1 to the user story generator.
What each field asks for
| Field | What to enter |
|---|---|
| Story map | Root: product or goal. Below: activities, then steps, then stories. |
| Persona | Who walks through the map (optional). |
| How many releases to slice | The first is always the walking skeleton. |
Example
A fictional salon booking app maps the path of someone booking on the phone: 3 activities (find a slot, book, attend), 6 steps and 13 stories. Release 1 brings together 6 stories, one per step, such as seeing the list of services with prices and getting a reminder the day before. Release 2 adds the second story of each step, such as signing in with a saved account, and only "see photos of previous work" is left for release 3 onwards.
When to use
- At the start of a product or a large feature, to see the whole flow before prioritising.
- When the backlog has become a long list and nobody knows the smallest useful delivery.
- To plan releases that deliver the end-to-end flow from the very first one.
- In a workshop with the team, to align on the user’s path.
Frequently asked questions
What is a user story map?
It is a way of organising the backlog in two dimensions: horizontally, the user’s path (activities and steps); vertically, the stories for each step, from the most essential to the least. The team sees the whole picture, not just a list.
What is the walking skeleton?
It is the first release: a simple version of every step, so the flow works end to end. It delivers value early and exposes integration problems before the product grows.
What is the difference between an activity, a step and a story?
An activity is a big stage of the path (book). A step is an action within it (confirm the slot). A story is a concrete way of doing the step (confirm with name and phone number).
How many levels should the map have?
Three below the root are enough: activities, steps and stories. If a story looks too big, split it in the user story generator instead of adding a fourth level.
How do I order the stories under each step?
Put the simplest way of completing the step at the top and, below it, the variations that improve the experience. The tool uses this order to suggest the release slices.
What is the difference between a story map and a customer journey?
The journey describes the current or desired experience, with emotions and touchpoints. The story map starts from the same path, but to decide what to build and in what order.