User Story Mapping

Purpose

User Story Mapping, created by Jeff Patton, arranges user stories in a two-dimensional map. The horizontal axis shows the user's journey (activities and tasks); the vertical axis shows priority from walking skeleton to full feature. This gives the team the big picture that a flat backlog hides.

At a glance

How to run

1. Identify personas (10 min) — Who are the primary users? Pick 1–3 personas to map.
2. Map the backbone (20 min) — Walk through the user's journey at the highest level. Write each major activity on a card and place them left to right. These form the backbone.
3. Break into tasks (30 min) — Under each activity, list the user tasks in priority order (most essential at top). These are the body of the map.
4. Add details (20 min) — Below each task, add specific stories, acceptance criteria, or UI sketches.
5. Draw release lines (20 min) — Draw horizontal lines across the map. Everything above the first line is the MVP. The second line is Release 2, and so on.
6. Validate (10 min) — Read the MVP line left-to-right as a story: "A user can [activity 1 tasks] and [activity 2 tasks] and ..." Does it make sense as a coherent product?
7. Transfer to backlog (10 min) — Each slice becomes a release, each card a backlog item.

Materials needed

• Large wall (3+ meters) or digital whiteboard
• Sticky notes (different colours for activities, tasks, details)
• Persona descriptions
• Markers

Pitfalls & common mistakes

• Map is too detailed — Start broad, add detail only where needed for the next release.
• No release slicing — A map without horizontal slices is just a big picture with no delivery plan.
• Missing personas — Without a clear user in mind, the map becomes system-centric.
• Only the PO maps — The whole team should participate to build shared understanding.

Inclusion & accessibility

• Use large, readable handwriting or typed cards.
• Walk through the map aloud for remote participants.
• Provide persona descriptions in advance.
• Use colour plus position (not colour alone) to indicate priority.

Variations

• Discovery story map — Map first, then do user research to validate assumptions.
• Story mapping for existing products — Map the current user journey, then identify gaps and improvements.
• Impact mapping + story mapping — Start from impact goals, then map the user journey to achieve them.

When NOT to use this

• If the product has a single, simple workflow with no meaningful journey to map.
• If the team already has deep shared understanding of the user journey — jump to release planning.

Source & further reading

• Patton, J. (2014). *User Story Mapping*. O'Reilly.
• Patton, J. (2005). "It's All in How You Slice It." jpattonassociates.com