User Story Mapping Workshop Template

A flat backlog is a prioritized list. A story map is a two-dimensional view: the user's journey runs left-to-right (time/sequence), and priority runs top-to-bottom. The flat backlog tells you what to build next. The story map tells you why you are building it and how it fits into the user's experience. Use both: the story map for context and scope decisions, the backlog for sprint-level execution. For more on building effective backlogs, see the [how to build a product roadmap guide](/guides/how-to-build-a-product-roadmap).

During the workshop, keep stories at the "user task" level. Each story should describe one thing a user does, not an implementation detail. "User can filter results by date" is the right level. "Add date picker component to the search results page" is too detailed. You will decompose stories into implementation tasks later during sprint planning.

When two people disagree about whether a story is MVP-critical, ask a forcing question: "If we shipped without this, would a user be able to complete the workflow and get value?" If yes, it goes below the MVP line. The goal of the MVP is the thinnest viable slice, not the ideal first version. Features that make the experience better but are not required for the workflow to function belong in v1.1.

Yes. Story mapping works well for major feature areas, redesigns, or new workflows within existing products. Scope the workshop to the specific workflow you are building or redesigning. The backbone should reflect the user's journey through that workflow, even if other parts of the product already exist. It is also useful when the team has lost track of how a large feature area fits together.

Miro and FigJam are the most popular. Both support sticky notes, grouping, and horizontal/vertical organization. For teams already using Jira or Linear, you can map first in Miro and then create tickets from the map. The [Product Operations Handbook](/product-ops-guide) has recommendations on tooling workflows that connect discovery artifacts to delivery tools. ---