methodatlas
Method guideProduct Discovery

User Story Mapping

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium
Time2-4 h
Participants4-10
FormatWorkshop
MaturityCanonical
Plan the map
01

Prerequisite

What needs to be finished first

Complete firstUser and goal

A specific user group and relevant goal are named.

A solution-centered feature list does not describe a user journey.
Complete firstShared perspectives

Product and delivery knowledge are represented; user evidence or explicit assumptions are available.

Untested team beliefs must not be presented as user facts.
02

Preparation

What needs to be ready before start

Materials

A wall or digital board, cards in two sizes or levels, markers, user-flow or research evidence and space for horizontal release lines.

People / roles

A cross-functional group from product, design, engineering and domain roles. Facilitation protects the user perspective and prevents premature release commitments.

Pre-read

Gather relevant user research, existing backlog cards, constraints and target outcomes. Mark hypotheses.

Time needed

About 2–4 hours for a focused first pass; extend extensive journeys across sessions.

Setup

Make the map readable from left to right. Put activities above concrete tasks and variants. Consider release slices across the task flow.

03

Core question

The one question this method answers

How do users move from their starting point to their goal, and which smallest coherent deliveries support them?

04

Flow

Phases with goal, actions, output and pitfall

User Story Mapping organizes user activities and concrete tasks into a readable narrative. Teams use vertical detail and horizontal slices for shared prioritization and release conversations.

Story Map: Borrow a tool

Fictional teaching example

Fictional activity flow with example tasks in each release slice. In the actual map, task cards sit beneath the horizontal backbone.

Story Map: Borrow a tool
Release sliceChoose a toolSecure the loanCollect the toolReturn the tool
First thin end-to-end sliceWhich smallest task makes this part usable for the user?Choose a tool and available time.Confirm the reservation.Identify and collect the tool.Return it at the agreed time and place.
Improve reliabilityWhich additional task reduces relevant friction?Filter tools by intended use. (later)Show how to change or cancel.Confirm location and opening hours.Offer a reminder and extension request.
Later options and variantsWhich exceptions or enhancements remain deferred?Add consumables.Waitlist for unavailable tools.Explore accessible handover options.Record and resolve damage.

  1. 1. Choose a tool

    First thin end-to-end slice
    Choose a tool and available time.
    Improve reliability
    Filter tools by intended use. (later)
    Later options and variants
    Add consumables.

  2. 2. Secure the loan

    First thin end-to-end slice
    Confirm the reservation.
    Improve reliability
    Show how to change or cancel.
    Later options and variants
    Waitlist for unavailable tools.

  3. 3. Collect the tool

    First thin end-to-end slice
    Identify and collect the tool.
    Improve reliability
    Confirm location and opening hours.
    Later options and variants
    Explore accessible handover options.

  4. 4. Return the tool

    First thin end-to-end slice
    Return it at the agreed time and place.
    Improve reliability
    Offer a reminder and extension request.
    Later options and variants
    Record and resolve damage.

All activities and cards are fictional. A walking skeleton is a thin end-to-end path, not a guarantee of a finished product.

Source: Jeff Patton

  1. 1

    Frame

    Set the user and goal

    Goal

    The map tells a coherent user journey.

    Inputs for this step

    • User knowledge or research
    • Product goal and scope

    Actions

    • Name the user type and trigger.
    • Distinguish the user goal from an internal project goal.
    • Define the beginning and end of the experience.

    Output

    Shared story-map frame

    User · goal · start and end

    Quality check

    Is the map told from one user group’s perspective?

    Pitfall

    Multiple user groups and goals are mixed in one map. Choose one primary journey and mark alternate paths explicitly.

    Timing: About 15 minutes.

  2. 2

    Backbone

    Order activities and tasks

    Goal

    The map shows the flow from left to right and exposes gaps.

    Inputs for this step

    • User goal and relevant cases
    • Shared wall or board

    Actions

    • Arrange activities as short action phrases across the journey.
    • Collect concrete user tasks under each activity.
    • Order tasks in sequence and mark alternate paths.

    Output

    Backbone with user tasks

    Activities left to right · tasks beneath

    Quality check

    Do the activities cover the user journey end to end?

    Pitfall

    Headings describe system modules or teams rather than user activities. Name activities from the perspective of what the person wants to do.

    Timing: About 45 minutes.

  3. 3

    Detail

    Add variants and gaps

    Goal

    Prioritization rests on a sufficiently shared picture.

    Inputs for this step

    • Backbone and tasks
    • User evidence or explicitly marked open assumptions

    Actions

    • Add missing steps, decisions and recovery paths.
    • Attach sources or assumption labels to uncertain tasks.
    • Group dependencies and variants so the main narrative remains readable.

    Output

    A fuller task flow with open points

    Primary flow · variants · evidence or assumption

    Quality check

    Are critical tasks or user questions missing?

    Pitfall

    The map looks complete while mostly reflecting team assumptions. Keep user questions visible and agree on targeted research before product decisions.

    Timing: About 40 minutes; develop large maps over multiple blocks.

  4. 4

    Slices

    Slice end-to-end releases

    Goal

    The first delivery is a thin, usable path rather than an isolated feature.

    Inputs for this step

    • Task map and shared goal
    • Delivery, risk and dependency knowledge

    Actions

    • Select the necessary top tasks and draw a horizontal slice across essential activities.
    • Check that the first usable end-to-end path works; mark it as a walking skeleton when it supports a complete flow.
    • Discuss later slices in light of user value, risks and dependencies.

    Output

    Story map with justified release slices

    End-to-end slice · dependencies · open questions

    Quality check

    Does the first slice support a complete user journey? Are omissions and later additions visible?

    Pitfall

    The horizontal line selects many top tasks without delivering end-to-end value. Walk through the slice using a concrete user goal and revise its scope.

    Timing: About 30 minutes.

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

User Story Mapping · Journey und Release-SlicesNutzeraktivitäten als Backbone legen, Stories darunter sammeln und lieferbare Releases schneiden
User Story MappingEine Story Map zeigt ein User Goal, Aktivitäten als Backbone, darunter Stories und horizontale Release-Slices.Journey-Backbone und lieferbare Releases gemeinsam schneidenAktivitäten bilden den oberen Ablauf, Stories darunter werden in MVP und spätere Ausbaustufen sortiert.User GoalBestellung erfolgreich abschließenEntdeckenAuswählenKaufenErhaltenNutzenRelease 1 · MVPRelease 2 · AusbauSucheFilterProdukt ansehenVergleichenCheckoutGutscheinTrackingRetourenBewertenSupport
Form

A shared story map with user goal, activity backbone, tasks, variants, release slices, sources and open assumptions.

Versioning / ownership

Record user group, scope, date and slice decisions. Version release lines, removed cards and changes; do not treat the map as a delivery-date commitment.

Tool alternatives
  • Cards or digital sticky notes
  • Large wall or shared board
  • Optional backlog export for moving cards

user-story-mapping-working-template.md

Plan a shared map from user activities through initial release slices.

User Story Mapping: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Map a user journey Time: About 2–4 hours for a focused first pass

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: A wall or digital board, cards in two sizes or levels, markers, user-flow or research evidence and space for horizontal release lines.
  • Roles: A cross-functional group from product, design, engineering and domain roles. Facilitation protects the user perspective and prevents premature release commitments.
  • Advance information: Gather relevant user research, existing backlog cards, constraints and target outcomes. Mark hypotheses.
  • Overall time needed: About 2–4 hours for a focused first pass; extend extensive journeys across sessions.
  • Setup: Make the map readable from left to right. Put activities above concrete tasks and variants. Consider release slices across the task flow.

Prepare for the work steps

Frame: Set the user and goal

  • User knowledge or research
  • Product goal and scope

Backbone: Order activities and tasks

  • User goal and relevant cases
  • Shared wall or board

Detail: Add variants and gaps

  • Backbone and tasks
  • User evidence or explicitly marked open assumptions

Slices: Slice end-to-end releases

  • Task map and shared goal
  • Delivery, risk and dependency knowledge

Story Map: Borrow a tool

Release sliceActivity 1Activity 2Activity 3Activity 4
First thin end-to-end slice
Improve reliability
Later options and variants
  • First thin end-to-end slice: Which smallest task makes this part usable for the user?
  • Improve reliability: Which additional task reduces relevant friction?
  • Later options and variants: Which exceptions or enhancements remain deferred?

Blank worksheet: name the backbone from the real user journey; stack task cards under each activity and draw horizontal release lines across the map.

Source: Jeff Patton

Frame: Set the user and goal

Expected artifact: Shared story-map frame

User · goal · start and end

Entry:

...

  • Is the map told from one user group’s perspective?

Backbone: Order activities and tasks

Expected artifact: Backbone with user tasks

Activities left to right · tasks beneath

Entry:

...

  • Do the activities cover the user journey end to end?

Detail: Add variants and gaps

Expected artifact: A fuller task flow with open points

Primary flow · variants · evidence or assumption

Entry:

...

  • Are critical tasks or user questions missing?

Slices: Slice end-to-end releases

Expected artifact: Story map with justified release slices

End-to-end slice · dependencies · open questions

Entry:

...

  • Does the first slice support a complete user journey?
  • Are omissions and later additions visible?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/user-story-mapping/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

user-story-mapping-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Tool lending

All details are invented. This map is an illustration, not user research or a prioritized delivery plan.

User goal: A household arranges a tool for a planned repair.

Backbone: Choose a tool → secure a loan → collect it → return it.

Thin first slice: Choose a tool, see availability, confirm a reservation, collect it and return it on time.

Next slice: Clarify cancellation, opening hours and extensions.

Later: Waitlist, consumables and damage handling.

Open question: Does the fictional reservation flow cover different repair situations? Real cases would be needed.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Set the user and goalMultiple user groups and goals are mixed in one map.View in phase
  2. Order activities and tasksHeadings describe system modules or teams rather than user activities.View in phase
  3. Add variants and gapsThe map looks complete while mostly reflecting team assumptions.View in phase
  4. Slice end-to-end releasesThe horizontal line selects many top tasks without delivering end-to-end value.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

User group or goal remains unclear: improve the context and evidence first.
The map grows without a readable narrative: focus the primary journey and separate variants.
A release slice contains only internal infrastructure without a usable outcome: revisit the user journey.
Release dates or effort are inferred from the map: assess estimates and dependencies with the delivery team separately.

Where to go next?

Story Splitting method illustration showing its working structure
Agile
Story Splitting

Breaks a chosen release slice further down into deliverable small stories.

Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping

Clarifies one story from the backbone with rules and examples.

View in playbookCreate Backlog ReadinessMove from rough ideas to shippable stories with examples, acceptance criteria, and estimation.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods