domains / families / business / user-story-mapping

user-story-mapping

separate

Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.

When to use

• Visualize the user journey by creating a hierarchical map that breaks down high-level activities into steps and tasks, organized left-to-right as a narrative flow. Use this to build shared understanding across product, design, and engineer…

When not to use

• For trivial features (don't map what you already understand)
• When user workflows are constantly changing (map stabilizes workflows)
• As a replacement for user stories (the map informs stories, doesn't replace them)
• Project management (not a Gantt chart)
• Feature listing (activities aren't features—they're user behaviors)

Skill page

Source