Story Mapping
Developed by Jeff Patton, a User Story Map arranges user stories spatially to reveal the full scope of a product or feature and enable intelligent slicing. The horizontal axis represents the user's journey (activities and tasks from left to right). The vertical axis represents priority — the top row is the minimal viable set. Story mapping prevents teams from building features in isolation from user flow.
Comment l'animer
- 1
Define the user and the backbone: the high-level activities the user performs (e.g. Search → Select → Purchase → Receive).
- 2
Place backbone activities as column headers across the top in sequence.
- 3
Under each activity, list the specific tasks or stories that make up that activity.
- 4
Sort tasks vertically by priority within each column.
- 5
Draw a horizontal line to define the MVP — everything above the line is the minimum viable product.
- 6
Everything below the line is future releases.
- 7
Review the map: does the MVP tell a complete user story? Are there gaps?
Conseils
The backbone is the most important part — if the top-level activity sequence is wrong, everything below is wrong.
Don't let the map become a backlog dump; it should tell a coherent user story at every horizontal cut.',
Variantes
Run a 'Now/Next/Later' variant replacing MVP cuts with time horizons. Use Story Mapping for marketing campaigns, content calendars, or customer success journeys — not just software.
Contextes d'utilisation
Planifiez votre prochain atelier avec l'IA
Workshop Weaver vous aide à combiner des méthodes comme Story Mapping en un agenda complet et minuté en quelques minutes.
Essayer gratuitementMethod descriptions on Workshop Weaver are original content written by our team, based on established facilitation practices.