> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/ux-methods/ideation/user-story-mapping.md).

# User Story Mapping

User story mapping is a collaborative technique used to visualise and organise user stories in a structured and meaningful way.&#x20;

It involves creating a visual representation of the user journey or product flow by arranging user stories into a cohesive narrative. User story mapping helps teams gain a holistic view of the product or project and facilitates the identification of user needs and priorities.&#x20;

The technique typically involves using sticky notes or cards on a wall or digital platform to arrange user stories in a logical sequence, capturing the user's experience from start to finish.&#x20;

By creating a user story map, teams can identify dependencies, gaps, and opportunities for delivering value to users. It aids in prioritisation, backlog refinement, and ensures that the development efforts are focused on addressing user needs and achieving desired outcomes.

#### Further Reading

{% embed url="<https://www.nngroup.com/articles/user-story-mapping/>" %}

{% embed url="<https://www.interaction-design.org/literature/article/user-story-mapping-in-design>" %}

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=TaMLUf3gISo>" %}

{% embed url="<https://www.youtube.com/watch?v=AnQpmomm7wA>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.designreference.xyz/ux-methods/ideation/user-story-mapping.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
