A product's story left to right, sliced into releases with the cut line drawn.
1 user story map example
Reporting feature story map
Four activities of a reporting feature sliced into MVP, a second release and later.
Columns are the story in narrative order and rows are release slices. The release cut under MVP is the editorial point, and the one risky story, row-level permissions, is flagged before anyone commits to the date.
A user story map arranges user stories in two dimensions: horizontally the activities a user goes through in order, the backbone, and vertically the stories under each activity, ordered by priority. Jeff Patton introduced the technique.
Read the top row left to right as the user's journey. Horizontal lines slice the stories below into releases, and the first cut line marks the minimum set that delivers the journey end to end.
When to use a user story map
Use it to plan an MVP or a new feature, such as reporting, so the first release covers the whole journey thinly.
Use it to replace a flat backlog that has lost the context of what users are trying to do.
If the scope is already fixed and you need dates, move to a Gantt chart or roadmap.
How to make a good user story map
Write the backbone as user activities with verbs, not as system modules.
Keep stories small and user-facing, in the user's words.
Draw release slices as clear horizontal lines and name each release by its outcome.
Build it together with the team; the conversation matters as much as the map.
