User Story Map Template

What this template is for

A user story map gives your backlog a shape — instead of a flat list that loses context, you get a two-dimensional view where the horizontal axis shows the user journey and the vertical axis shows priority by sprint. This template is structured around three epics, each with two activities, and stories distributed across Sprint 1, Sprint 2, and the Backlog. It is built for product managers, agile coaches, and scrum teams who want to move from feature lists to a delivery plan that the whole team can read in under a minute. Use it before sprint planning to align on scope, in stakeholder reviews to show sequencing decisions, or as a living document throughout the quarter.

When to use this template

• Align a cross-functional team on what is in scope for the next release before sprint planning starts.
• Show stakeholders why certain features are in the backlog and not Sprint 1 without a lengthy explanation.
• Identify gaps in the user journey by checking whether all critical activities have at least one Sprint 1 story.
• Run a remote story mapping workshop by sharing the canvas and letting team members add stories collaboratively.
• Communicate a phased MVP to a client — Sprint 1 is the launch, Sprint 2 is the follow-up, Backlog is future.
• Onboard a new product manager by giving them a visual overview of the existing backlog structure.

How to use it

1. 1Write the top-level user activities across the top of the canvas — these form the backbone of the map.
2. 2Group activities under epics (themes or user goals) in the row above them.
3. 3Add user stories under each activity — each story should describe one slice of value for one type of user.
4. 4Drag stories vertically to assign them to Sprint 1, Sprint 2, or Backlog based on priority and dependencies.
5. 5Draw a horizontal line between sprint sections to make the delivery boundaries clear.
6. 6Review the map with the team: does every Sprint 1 story directly serve a user goal in the backbone?

Quick example