# Experience Map

An experience map shows broad human activity across contexts, independent of one product, to reveal needs and opportunities beyond current touchpoints.

- Type: artifact
- Domain: Leadership & teams
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/experience-map/>)

## What it means

An experience map is a broad visualization of how people experience an activity or domain over time, such as managing chronic pain or relocating to a new city. It is usually product-agnostic and may include multiple channels and providers. Compared with a customer journey map, it explores a wider human context rather than one persona’s relationship with one service.

## Why it matters

Product boundaries can hide the real problem. People improvise with spreadsheets, family help, competitors, public services, and offline work long before or after they touch a product. An experience map helps leaders avoid local optimization, see unmet needs across the wider activity, and choose where the organization can responsibly contribute.

## When to use it

Use it during early discovery, portfolio strategy, new-market exploration, or when several products address fragments of the same human goal. It is especially useful when the team needs to understand a domain before selecting a specific service concept or target journey.

## How it works

1. Frame a human activity and time horizon without defining the opportunity solely around the existing product.
2. Recruit a varied set of participants and research behavior across contexts, including workarounds, nonuse, other providers, and social support.
3. Synthesize common phases, goals, actions, environments, actors, emotions, barriers, and transitions while retaining important differences.
4. Plot current organizational touchpoints as only one layer, then identify gaps, leverage points, harms, and opportunities beyond those touchpoints.
5. Use the map to frame hypotheses and research priorities, not to claim that one generalized path predicts every person.

## A practical example

A mobility company maps the experience of getting to recurring medical appointments, from scheduling and arranging childcare to navigating buildings and returning home. The map shows that missed trips are often caused by appointment changes and caregiver coordination, leading the team to explore shared notifications and flexible rebooking rather than only faster vehicle matching.

## Where it breaks

Breadth can make an experience map vague, expensive, and difficult to act on. Patterns may flatten cultural and structural differences, while an overly ambitious map can become a mural no team owns. Narrow the domain enough to research well, show confidence and variation, and follow broad mapping with focused studies before committing resources.

## Common mistakes

- Relabeling a product funnel as an experience map.
- Generalizing from a small homogeneous sample across a broad population.
- Listing opportunities without checking organizational role, feasibility, consent, or possible downstream harm.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/experience-map/#visualization-experience-map>)

## Sources

1. [UX Mapping Methods Compared: A Cheat Sheet](<https://www.nngroup.com/articles/ux-mapping-cheat-sheet/>) — Nielsen Norman Group · Professional guidance
2. [Mapping Journeys](<https://www.thisisservicedesigndoing.com/methods/mapping-journeys>) — This is Service Design Doing · Method guide

## Related topics

- [Customer Journey Map](<https://wiki.soroush.uk/topic/customer-journey-map/>)
- [Ecosystem Map](<https://wiki.soroush.uk/topic/ecosystem-map/>)
- [Product Discovery](<https://wiki.soroush.uk/topic/product-discovery/>)
