User Story Mapping

When to use User Story Mapping

Use this method when starting a new project, defining a product roadmap, or needing to align the team around user needs and priorities.

What it solves

Lack of shared understanding of user needs, scope creep, difficulty prioritizing features.

How to run User Story Mapping, step by step

1. Identify the user persona. (5 min)
2. Define the user's main activities or goals. Write these on sticky notes and place them across the top of the board. (10 min)
3. Under each activity, brainstorm the specific tasks or steps the user takes to achieve that goal. Write each task on a sticky note and place it under the relevant activity. (20 min)
4. Prioritize the tasks within each activity based on importance and frequency. (15 min)
5. Discuss and refine the map as a team. (10 min)

Materials needed

• Sticky notes
• Markers
• Large whiteboard or wall
• Timer

Facilitator tips

• Encourage diverse perspectives from team members.
• Focus on the user's perspective throughout the process.

Common pitfalls

• Getting bogged down in details early on. Focus on the big picture first.
• Forgetting to prioritize tasks. Ensure the team agrees on the most important tasks.

Variations

• Create multiple user story maps for different user personas.
• Use different colored sticky notes to represent different types of tasks (e.g., functional, technical, UI).

Running it online or hybrid

Use a digital whiteboard like Miro or Mural to collaboratively create and organize user stories.

What it produces

A visual map of user stories organized by user activities and tasks.

Origin

Adapted from GOV.UK Service Manual — source

Build a session around User Story Mapping

METODIC places User Story Mapping inside a complete, timed session plan — agenda, worksheets, facilitator guide and slides — matched to your group and goal.

Generate a session with User Story Mapping · Try METODIC free