User story mapping: a how-to guide

Get a project’s requirements into one shared picture, agree what matters first, and start building sooner.

Sophie Collins

on

User story mapping is a workshop technique for agreeing what a new system needs to do. The team lays out every task a user takes, in order, then groups and slices those tasks to decide what to build first.

A new software project usually starts with a long list of requirements that nobody quite agrees on. Different people describe the same system in different ways, and a long document hides the gaps until development is underway.

Story mapping fixes that. You come out with one picture of the whole system that everyone has helped make.

We use it in our product discovery work, building on the method developed by Jeff Patton. This guide shows you how to run a session yourself, step by step, with a free template to download.

Updated November 2026. We first published this guide in 2019. The method still holds up, but the way teams run sessions has moved on, with many now held remotely or across hybrid teams. This update adds new step-by-step diagrams, a free story map template, advice on running sessions remotely, a section on when to bring in outside help, and answers to common questions.

Is this guide for you?

It’s written for you if:

  • You’re starting a new system and struggling to get your arms around the breadth of requirements.
  • A long requirements document is slowing your team down rather than guiding it.
  • You’re new to story mapping and want the basics before you run your first session.

What is user story mapping?

User story mapping is an Agile technique for working out what a new system needs to do, by mapping what its users will do with it. Each task a user takes goes on its own card. The cards are laid out in the order users would take them, grouped into activities, then sliced into releases.

The result is a map of the whole system that reads left to right as a story. It’s used by teams of every size, from start-ups to large organisations, for gathering requirements and for getting a group to agree on an idea.

What does a story map settle that a requirements document doesn’t?

A requirements document lists what a system must do. A story map shows how those requirements fit together around the people using them, which makes it easier to see what’s missing and what matters most. It helps a team

  • see the whole system at once, and how the parts connect
  • reach a shared understanding, because the visual format gets people talking and correcting each other early
  • focus detail on the most important features first, rather than specifying everything up front
  • describe the system from the user’s side, which keeps their needs in view
  • spot gaps and uncertainty that a flat document would hide

It can move a stuck project quickly. After one session we ran, a leading membership organisation told us: “We have made more progress in five hours than we have done in 18 months.”

If you remember one thing, make it this: the map’s main job is shared understanding. The cards matter less than the agreement the team reaches while placing them.

How do you set up a story mapping session?

You need the right mix of people, a big surface to work on, and the context from earlier discovery work in view.

Who should be in the room?

Bring together the people who understand the users, the business and the technology: typically a product owner, people from the teams who’ll use or support the system, and someone from the development team. The group can change from session to session, but the map is always built together, so priorities get argued out in the open rather than decided by whoever writes the document.

What should you have to hand?

Put anything that helps people picture the system where everyone can see it: personas, the product vision, wireframes or early designs. These keep the conversation grounded in real users rather than opinions.

In person or remote?

Both work. In a room, sticky notes on a wall are hard to beat for getting people moving and talking. Remote or hybrid sessions work well on a shared digital whiteboard such as Miro or FigJam, and you end up with a digital map from the start. Either way, keep one card per task, because you’ll be moving them around a lot.

How do you build a user story map, step by step?

The example below maps a simple ecommerce site, following the tasks a user takes to buy a product. The same map grows through each step, so you can follow along with the template and try it yourself.

Step 1: identify the tasks

Write down the tasks a user takes to buy something, one task per card. Keeping to one task per card matters, because you’ll be reordering them in the next step.

 Seven task cards scattered at different angles: View details, Search products, Enter delivery details, Compare options, Pay, Add to basket and Browse categories.

Step 2: tell the story

Put the tasks in order, from the first to the last. As you go, talk through what the user is doing at each point and why.

The seven task cards in one row, in journey order: Search products, Browse categories, View details, Compare options, Add to basket, Enter delivery details and Pay. An arrow beneath shows the order of the journey.

Step 3: share viewpoints

Now someone else talks through how they think a user moves through the site. Duplicates show where you already agree. Differences aren’t a problem: different users use a system differently, and finding the alternatives now gives you a truer picture of how it will be used.

The seven-card row, labelled "Your journey". Beneath it is a row of dashed cards labelled "A colleague's journey": Search products, under its matching card, and two new tasks, Read reviews and Collect in store.
Dashed cards are a colleague’s version. The duplicate shows agreement; the new cards show journeys you hadn’t thought of.

Step 4: add more as understanding grows

Merge everyone’s version into one flow. Group duplicates, then look for what’s missing: alternatives, exceptions and steps nobody mentioned. At this stage you’re still working on breadth, not depth.

The merged map. Search products is now a stack of two cards. Three alternatives sit beneath the main row: Read reviews under Compare options, Collect in store under Enter delivery details, and Pay with saved card under Pay.
Duplicates are grouped into one stack. Alternatives sit beneath the task they replace.

Step 5: group tasks into activities

Some tasks naturally belong together because they serve a bigger goal, such as finding a product or paying for it. Group these into activities along the top of the map. Requirements that cut across the whole journey, such as GDPR, can be grouped into an epic.

The map with three activity headings above the tasks: Find a product, over Search products and Browse categories; Choose, over View details and Compare options; and Buy, over the remaining three tasks. A dashed band at the bottom, labelled "Epic: GDPR", holds Cookie consent and Consent at checkout.
Navy bars are activities, groups of related tasks. The dashed band is an epic, a requirement such as GDPR that cuts across the journey

Step 6: start slicing

Slicing means drawing a line across the map to separate what’s needed for a particular outcome from what can wait. You can slice by release, or, as here, by the minimum needed to complete one essential journey: buying a product. This is where the group agrees priorities, and it’s often where the most useful arguments happen.

The map split into two parts. A shaded band labelled "First release: buy a product" holds Search products, View details, Add to basket, Enter delivery details and Pay. Under "Later" sit Browse categories, Compare options, Read reviews, Collect in store and Pay with saved card. The GDPR epic band stays at the bottom.
Tasks in the shaded band are the minimum needed to buy a product. Everything under “Later” can wait for a future release

Step 7: get into the detail

Now expand the tasks in your first slice, most important first. What information do you need from the user? What validation rules apply? What does the user need to see? What value does each task give them?

The sliced map with two small detail cards under each first-release task: Search by name and No-results help under Search products; Price and stock and Product images under View details; Update quantity and Basket total under Add to basket; Postcode lookup and Validate address under Enter delivery details; Card payment and Confirm order under Pay.
The small grey cards are the detail for each first-release task, such as validation rules and the information shown. These become acceptance criteria later.

What happens after the session?

The map becomes the team’s working reference for the rest of the project. It isn’t a discovery deliverable that gets filed away; it grows as understanding grows, and it should stay in view during development alongside the product vision.

The tasks in your first slice get the most detail first. The rest get filled in as development goes on, so each new piece of work benefits from what the team has learned so far, including any changes in what users need.

When a feature is understood well enough to build, its tasks become user stories in the backlog. The detail from step 7 becomes the acceptance criteria used to check the feature is complete.

This is how story mapping replaces the long requirements document typical of waterfall projects. Requirements written down too early go out of date quickly. That doesn’t mean no documentation: keep the map digital so it’s easy to update, and use it to show progress. One simple approach is to colour each card by status (not started, in progress, done), which shows where a project stands far more clearly than a chart.

Can you use story mapping for anything else?

Yes. You can map an existing system’s processes to spot where they’re inefficient, or use the same approach as a roadmapping tool for a wider strategy or improvement plan.

Download the free story map template

The download has two pages. The first is a one-page quick guide to the seven steps, to keep to hand during the session. The second is the template itself: activities along the top, a first-release band, a row for later releases, and an epic band for requirements that cut across. Print it, or use it as the layout for a digital board.

When should you run it yourself, and when should you bring someone in?

If your team broadly agrees on what it’s building and someone can facilitate without a stake in the outcome, run it yourself. The template and the steps above are enough to get a useful first map.

It’s worth bringing in an outside facilitator when the session itself is likely to get stuck. The signs to look for:

  • The stakeholders don’t agree on what the system is for. A facilitator with no stake in the answer can keep the argument on the map, rather than on who’s in the room.
  • You’re replacing a system nobody fully understands. Mapping the current processes first often turns up requirements that only exist in people’s heads.
  • There’s no clear product owner. Without someone who can make the call, slicing stalls, because every task looks essential to somebody.
  • The map keeps growing but won’t settle. If every session adds cards and nothing moves into a first release, the problem is usually priority, not missing tasks.

Story mapping is one part of how we run product discovery at Box UK, alongside user research, technical planning and roadmapping. If your project is at the point where requirements are sprawling and agreement is hard to come by, that’s usually the right time to talk.

Sophie Collins

UX Designer

Sophie, a UX and Agile enthusiast with a background in Product Ownership and Software Testing, brings pragmatism and quality to every stage of the software delivery lifecycle. With experience across industries like finance, insurance, and e-commerce, she has spoken at software conferences on agile practices and is a Certified Scrum Product Owner.

Frequently asked questions

What’s the difference between a user story map and a user journey map?

A user journey map describes a person’s experience, often including how they feel at each point, and is mostly used to understand a service as it is. A user story map breaks down the tasks a system has to support and is used to plan what to build and in what order. Journey maps often feed into story maps.

How is a story map different from a product backlog?

A backlog is a flat list in priority order. A story map keeps each task in the context of the user’s journey, so you can see what a release delivers end to end. The backlog is drawn from the map, not the other way round.

Who should facilitate the session?

Ideally someone who knows the method well and doesn’t own the outcome. A product owner can run it, but it’s harder to steer a debate about priorities when you’re also one of the people with a view.

Can you story map an existing system?

Yes. Mapping how a current system is actually used is a good way to find inefficiencies and hidden requirements before replacing it.

Do you need special software?

No. Sticky notes and a wall work well in person, and any shared digital whiteboard works remotely. The free template above gives you the layout either way.

Have a project you’d like to discuss?

Give us a call on 020 7439 1900 or fill in the form and we will get back to you.