In 30 seconds
- The backbone runs left to right: the user's main activities.
- Stories hang below each activity, most important at the top.
- Horizontal slices become releases.
How a story map is laid out
- Backbone: user activities in order, such as browse, choose, pay, track
- Stories: under each activity, ordered top to bottom by importance
- Slices: horizontal lines dividing releases
Jeff Patton developed the technique and described it in his 2014 book User Story Mapping.
Slicing releases
The first slice is the thinnest path through every activity, enough for a user to complete the journey end to end. Later slices make each step richer. This avoids building one activity perfectly while others don't exist.
Why it beats a flat backlog
A flat backlog hides the big picture. A map shows how stories fit together and where gaps are, making epics easier to split.
Myth vs reality
Myth · Story maps replace the backlog.
Reality · They feed it; the backlog remains the ordered list.
Myth · The map is done once.
Reality · It evolves as you learn.
Myth · Mapping is only for new products.
Reality · It also helps plan major features in existing ones.
FAQ
How long does mapping take?
A first map for a feature often takes a few hours.
Who should be in the session?
Product, design, developers and someone close to users.
Physical or digital?
Either; physical sticky notes work best in person.