User-story map

A user-story map arranges user stories in two dimensions. Across the top, left to right, runs the sequence of things a user does: the “backbone” of the experience. Beneath each step hang the stories that support it, with the most essential at the top and the optional or elaborate lower down. Jeff Patton developed and popularised the technique.

What problem it solves

A flat backlog is a list, and lists hide the product. After a few hundred stories nobody can say whether the thing hangs together, or why one story matters. The map restores the context: each story sits under the step it serves, so gaps in the flow are visible as empty space.

Slicing releases

The real use is planning. Draw a horizontal line across the map and everything above it becomes a release. The top slice is a thin but complete path through the whole experience, which is the heart of a good MVP: not half the steps in full, but every step in minimum form. Later slices deepen each step.

Story map versus journey map

A user journey map records the user’s experience, including feelings and pain points, and is a research artefact. A story map plans what the team will build, and is a delivery artefact. They share a left-to-right shape and often share the same early steps.

Common mistake

Mapping the product’s features instead of the user’s activity. The backbone should read as verbs a person performs, not as screens or modules.