artifactLeadership & teams

Experience Map

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

Download Markdown (.md)

01What 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.[1][2]

Broad human activity over time Map phases together with context, actors, emotion, barriers, and transitions
01Phases + transitions
How the wider activity unfolds over time
02Goals + actions
What people try to accomplish and do
03Contexts + actors
Environments, providers, communities, support
04Emotion + barriers
Variation, friction, harm, uncertainty
05Touchpoints + gaps
Current service role and opportunities beyond it

The organization's touchpoints are only one layer; the map should include workarounds, nonuse, other providers, and social support.

02Why 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.

03When 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.

04How 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.

05A practical example

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.

06Where 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.

07Sources

  1. UX Mapping Methods Compared: A Cheat SheetNielsen Norman Group · Professional guidanceUX Mapping Methods Compared: A Cheat Sheet
  2. Mapping JourneysThis is Service Design Doing · Method guideMapping Journeys
View saved topics

Start typing to search titles, definitions, categories, and frameworks.