> 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/scenario-mapping.md).

# Scenario Mapping

Scenario mapping is a collaborative user experience method used to visualise the steps a person takes to achieve a specific goal. It involves breaking down a user's journey into a chronological sequence of actions, thoughts, and emotions to see how they interact with a product or service. By laying out these steps on a timeline, a design team can identify where a user might feel confused or frustrated, allowing them to spot gaps in the current experience before any development begins.

The process usually begins with a specific persona and a clear objective, such as a customer trying to return a faulty item or a new user signing up for a subscription. The team then maps out every touchpoint and decision the user encounters. This physical or digital map serves as a shared source of truth that helps prevent misunderstandings between designers, developers, and stakeholders. It forces the team to move beyond abstract ideas and focus on the practical reality of the user's situation.

In the final stages, scenario mapping helps to prioritise which features are truly necessary and which can be simplified. By seeing the entire flow in one view, it becomes much easier to identify opportunities for innovation or points where the process can be streamlined. It is an essential tool for creating a seamless experience because it ensures that every part of the journey is designed with a deep understanding of the human context behind each click or tap.

#### Further Viewing

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

#### Further Reading

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

{% embed url="<https://www.uxforthemasses.com/scenario-mapping/>" %}

{% embed url="<https://www.whatifdesign.co/design-glossary/scenario-mapping>" %}

{% embed url="<https://ux-prasad.medium.com/scenario-map-cb83e658f7c0>" %}

{% embed url="<https://helio.app/ux-research/ux-deliverables/scenario-map/>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.