What Is a Story Map?
A story map is a way of laying out the work on a product so it follows what the user does. Across the top, left to right, are the things the user does in order. Under each one are the smaller pieces of work, with the most important at the top.
Jeff Patton described the method in his book User Story Mapping. A list of tasks does not show how the tasks fit together, but a map does. You can read it like a story, see where it is thin, and draw a line across it to decide what to build first.
The Parts of a Story Map
A story map has three rows.
- Activities. The big things the user does, in order. “Find a tool,” “Reserve it,” “Pick it up.” Usually five to ten of them.
- Steps. What the user does inside each activity. “Browse tools,” “Check details,” “Check availability.” Activities and steps together are called the backbone.
- Details. Everything under a step: user stories, features, questions, risks, and problems users have today. This is where most of the cards live.
The example above is for a tool library where members borrow drills and ladders. The same shape works for any product: a checkout, an onboarding flow, an internal approval process.
Reading the Map
Read left to right and you get the story of what the user does. Read top to bottom under any step and you get what matters most for that step.
For the vertical order, if the user could not get through the step without a card, it goes near the top. If they could, it goes down. Sorting happens within each step, not across the whole map.
Slices and Releases
Once the cards are in order, draw a line across the whole map. What is above the line is the first release. It should be thin, but it should let a user get from the start of the journey to the end. This first thin slice is called a walking skeleton.
Draw more lines for later releases. Each slice should have a name that says what a user can do after it ships: “First order,” “Repeat orders,” “Orders for a team.”
Story Map vs. Backlog
A backlog is a list. It is good for tracking what is next and bad for seeing the whole. Two hundred items in a list do not show you which part of the product they belong to, whether any part is missing, or whether release one lets a user do anything end to end.
A story map holds the same items, arranged by where they sit in the user’s journey. The list is still there. You can read it off the map. But you can also see the shape of the product.
A story map is also not a site map. If the top row names parts of your product, like “Dashboard” and “Settings,” you have drawn a site map. The top row of a story map names things the user does.
When to Use One
- Planning a new product or feature. Map the whole journey before writing tickets, so the first release covers it end to end.
- Getting a team to agree. Build the map together. Disagreements about what the user does show up as arguments about where a card goes.
- Understanding a product you did not build. Map what you know, mark what you do not, and go find out. See the solo exercise.
- Cutting scope. When a deadline moves, a map shows which cards can drop below the line without breaking the journey.
- Explaining a plan. A map is easier to walk someone through than a spreadsheet of tickets.
How to Build a Story Map
- Frame the problem. Write down who the user is and what they are trying to do.
- Map the backbone. Write the activities left to right, then the steps under each one.
- Fill in the details. Under each step, add the work, the questions, and the risks.
- Prioritize. Sort the cards under each step, most essential at the top.
- Slice. Draw a line for the first release. Check that a user can get all the way through above it.
For a full walkthrough with a worked example, read the story mapping team exercise. If you are mapping on your own, follow the story mapping solo exercise.
Terms You Will Hear
- Backbone. The activities and steps across the top of the map.
- Walking skeleton. The first slice. Thin, but the user can get from start to finish.
- Slice. A horizontal band of the map that makes up one release. In Cartographer these are milestones.
- Persona. The user the map is about. In Cartographer you can attach a persona to a map or to a card.
- Card. One item on the map. A card can be a story, a question, a risk, a pain point, or something you learned.
Story Mapping with Cartographer
Cartographer is AI for story mapping. Every board has the three rows, cards move by dragging, and Claude or ChatGPT can build the map for you. On top of that you get:
- An MCP server, so Claude or ChatGPT can read the map and add cards from notes, tickets, and interviews.
- Milestones for slices, and statuses and estimates on each card once you start building.
- Personas and customers, so you know who each card is for.
- Real-time editing, so a team can map together from different places.
- Shared views for people who need to see the map but not edit it.
Get Started
Create a free Cartographer account and build your first story map. If you want a walkthrough first, start with the team exercise.
