A visual planning technique that organizes user stories along two axes: the horizontal axis represents the user's sequential journey through a workflow, and the vertical axis represents increasing levels of detail or priority within each step. Story maps help teams cut coherent, user-centered vertical slices for MVP releases rather than delivering features as isolated, context-free chunks.
Common contexts
- Running a story mapping workshop with product and engineering to define the scope of a minimum viable product
- Reorganizing a cluttered backlog by placing stories on a map to reveal which steps in the user journey have no coverage
- Using a story map to negotiate MVP scope with stakeholders by showing what user outcomes each release enables
Use when
Use a user story map when a team is about to start scoping work for a new product or major feature — particularly when there's a risk that the backlog will be prioritized by technical convenience or stakeholder preference rather than by the coherent user journey the release needs to support.
Avoid when
Don't introduce story mapping on a mature product with a well-understood backlog and stable team rhythms unless there's a specific scoping problem to solve — the workshop overhead is high, and teams that are already aligned on user context won't gain proportionate value from the exercise.
A story map makes the horizontal backbone — the essential user activities — the hardest thing to cut, which is exactly right; the activities are the experience, and the stories below them are implementation details that should serve the backbone, not compete with it.
Real-world examples
- Spotify's launch planning for their podcast feature used a user story map to identify that 'discover new podcasts' was the backbone activity, allowing teams to prioritise editorial curation over advanced search for the v1 release.
- Jeff Patton, who invented user story mapping, used the technique with the US Digital Service team to redesign the Healthcare.gov application — the map revealed that CMS staff were the most underserved user group, shifting a major design priority.
- Atlassian's product teams story-map every major feature release, printing the map and pinning it to the wall in their team area — using its physical presence to keep developers and designers aligned on the full user journey during a 6-week build.