Experience Map

An experience map charts a whole real-world experience as a human lives it — across every tool, service, person, and workaround involved — WITHOUT centering any particular product. Buying a home, managing a chronic illness, planning a wedding, running a construction survey: the experience exists whether or not your product does, and the map draws it that way.

The NN/g distinction (Gibbons, "UX Mapping Methods Compared"): an experience map depicts an entire end-to-end experience, agnostic of a specific business or product — general human behavior; a journey map ties that experience to a SPECIFIC product or service and a specific user type. Practical consequence: you make the experience map first, when you don't yet have (or don't want to assume) a product; you make journey maps (User Journey Map, Customer Journey Map) after, once there's a product to map against.

What it's for

An experience map's job is to reveal where a product COULD fit:

• Unmet needs — stages where people cobble together spreadsheets, phone calls, and sticky notes because nothing serves them.
• Peak pains — the moments people describe with the most emotion in interviews; these anchor the opportunity list.
• The real competition — often not a rival app but a binder, a broker, or a brother-in-law who "knows about this stuff."
• Scope honesty — seeing the whole experience stops you optimizing your 5% of it while the other 95% determines whether anyone succeeds.

When to choose it over a journey map

• New markets: entering a domain you don't operate in yet — no product to map a journey against, so map the life instead.
• Complex life events: moving, bereavement, immigration, having a baby — long, multi-actor, emotionally loaded, spread across many institutions.
• Professional workflows: a surveyor's field day, a nurse's shift, a film editor's delivery week — the workflow spans many tools and your product will only ever be one of them.
• Strategy resets: when a team has stared at its own funnel so long it has forgotten the funnel is a minor subplot in the user's actual story.

If you already have a product and a defined user, and the question is "where does OUR experience hurt," use a journey map — it's sharper for that job.

Example: buying a first home (US)

Research → Budgeting → Touring → Mortgage Approval → Inspection → Closing → Moving → Maintenance

Reading the map: no single product owns this experience — a mortgage app touches one stage, a listing app two. The unmet needs sit in the gaps and handoffs (document re-sending, cost opacity, the missing "house system of record"), which is exactly the kind of insight a product-scoped journey map is structurally unable to produce.

Lineage

The modern experience map largely traces to Adaptive Path: Chris Risdon's "The Anatomy of an Experience Map" (2011) walked through the Rail Europe map — built from a 2,500-response survey plus field research with customers — and became the template practitioners copied. Adaptive Path later expanded the approach in its mapping work and UX Week talks (Risdon & Quattlebaum, 2012); Kalbach's Mapping Experiences generalizes the family as alignment diagrams. Note the irony fully: the canonical "experience map" was built for one company, so even the founding example blurs the experience-map/journey-map line the industry now argues about — one more reason to state your scope on the map itself.

How to build it

1. Field research first: interviews and observation with people living the experience — not your users, since the point is that there may not be a "your" yet (07-process-strategy/ UX Research Methods). Add quantitative shape where you can.
2. Draw stages as the person experiences them, including the boring and off-product ones.
3. Annotate per stage: tools/artifacts used, people involved, doing/ thinking/feeling (the emotion curve works here too — see file 04), and workarounds — workarounds are needs in costume.
4. Mark the gaps and handoffs between stages; that's the opportunity layer.
5. Only THEN overlay "where could we play" — as a separate layer, so the map stays honest when strategy changes.

Common mistakes

• Smuggling the product in: if your logo appears in every stage, you drew a journey map and titled it wrong.
• Interviewing only existing users — they're pre-filtered to people your current framing already fits.
• Stopping at pains without capturing the workarounds people ALREADY pay (time, money, favors) to solve them — that's the evidence a need is real.
• Making stages match your org's mental model of the domain instead of the lived sequence.
• Treating it as a one-off deliverable; experiences shift (rates rise, regulations change) and the map should be dated and revisited.

Checklist

• Scope is a human experience, named without your product in it
• Built from field research with people in the experience, not team memory
• Stages in lived order, including off-product and "boring" stages
• Tools, people/actors, and workarounds annotated per stage
• Emotion curve or peak-pain markers grounded in verbatims
• Gaps and handoffs between stages explicitly marked
• "Where we could play" is a separate overlay, not baked in
• Map dated; revisit trigger identified
• Follow-up journey map planned once a product scope is chosen

Sources

• Nielsen Norman Group — Gibbons, S. (2017). "UX Mapping Methods Compared: A Cheat Sheet" (nngroup.com/articles/ux-mapping-cheat-sheet/) — experience map as end-to-end and product-agnostic vs. journey map as product-specific.
• Risdon, C. (2011). "The Anatomy of an Experience Map." Adaptive Path (Nov 30, 2011; republished at articles.centercentre.com/ experience_map/) — the Rail Europe map and method.
• Risdon, C. & Quattlebaum, P. (2012). "Mapping Experiences and Orchestrating Touchpoints." UX Week 2012, Adaptive Path.
• Kalbach, J. (2016; 2nd ed. 2020). Mapping Experiences. O'Reilly.