> 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/discovery/customer-experience-mapping.md).

# Customer Experience Mapping

{% hint style="info" %}
AKA User Experience Mapping, Experience Maps, Experience Mapping
{% endhint %}

Customer experience mapping is a visual process used to understand the entire story of a person's interaction with a brand or service. It looks at every single touchpoint, from the moment someone first hears about a product to the final stage of support or renewal. By laying this out clearly, teams can see exactly how a customer feels at each step and where they might be facing difficulties.

Instead of just looking at one specific task, this method focuses on the person's emotions and motivations over time. It helps businesses identify gaps in their service where the experience might be inconsistent or frustrating. By seeing the world through the eyes of the user, a company can move away from internal assumptions and start making decisions based on real human behaviour.

The final map serves as a shared guide for everyone in an organisation, ensuring that designers, developers, and managers are all working towards the same goal. It makes it much easier to prioritise improvements that will have the biggest impact on customer satisfaction. Ultimately, this method is about building empathy and creating a smoother, more enjoyable journey for the people using a service.

#### Further Viewing

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

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

#### Further Reading

{% embed url="<https://blog.uxtweak.com/experience-map/>" %}

{% embed url="<https://www.nngroup.com/articles/ux-mapping-cheat-sheet/>" %}

{% embed url="<https://www.visual-paradigm.com/guide/user-experience-mapping/what-is-user-experience-mapping/>" %}

{% embed url="<https://uxmag.com/articles/how-to-build-an-experience-map-banner>" %}

{% embed url="<https://www.interaction-design.org/literature/topics/customer-experience-mapping?srsltid=AfmBOooTeOxx7jCzQuTKxb4aZ6dH1yT7Yt7vHRdub27KkNAxZroSkcQG>" %}

{% embed url="<https://uxdesign.cc/user-experience-mapping-alice-emma-walker-868259547ba8>" %}


---

# 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/discovery/customer-experience-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.
