Experience mapping skill

Experience Mapping

A guide to creating current-state experience maps that reveal customer pain points, emotions, and unmet needs -- turning interview data into actionable opportunities for the Opportunity Solution Tree.

What Is an Experience Map?

An experience map is a visual representation of how a customer accomplishes a specific goal today, capturing each step they take, what they think and feel at each step, and where they struggle. Unlike a journey map (which tracks interactions with your product), an experience map captures the customer's full experience regardless of which tools, products, or workarounds they use.

Experience Map vs. Journey Map

Aspect	Experience Map	Journey Map
Scope	The customer's entire experience of accomplishing a goal	Interactions with your specific product
Perspective	Customer-centered	Product-centered
When to use	Understanding the problem space; finding opportunities	Optimizing an existing product experience
Includes	Competitor usage, manual workarounds, offline steps	Your product's touchpoints only
Discovery value	High -- reveals unmet needs and new opportunities	Medium -- reveals friction in existing flows

Rule of thumb: In continuous discovery, start with experience maps. They reveal the full landscape of opportunities. Use journey maps later to optimize specific product flows.

Anatomy of an Experience Map

The Five Rows

A well-structured experience map has five horizontal rows that run across each step of the experience:

┌──────────┬──────────┬──────────┬──────────┬──────────┐
│  Step 1  │  Step 2  │  Step 3  │  Step 4  │  Step 5  │
├──────────┼──────────┼──────────┼──────────┼──────────┤
│  DOING   │  DOING   │  DOING   │  DOING   │  DOING   │
│ (actions)│ (actions)│ (actions)│ (actions)│ (actions)│
├──────────┼──────────┼──────────┼──────────┼──────────┤
│ THINKING │ THINKING │ THINKING │ THINKING │ THINKING │
│(questions│(questions│(questions│(questions│(questions│
│ & goals) │ & goals) │ & goals) │ & goals) │ & goals) │
├──────────┼──────────┼──────────┼──────────┼──────────┤
│ FEELING  │ FEELING  │ FEELING  │ FEELING  │ FEELING  │
│(emotions)│(emotions)│(emotions)│(emotions)│(emotions)│
├──────────┼──────────┼──────────┼──────────┼──────────┤
│  PAIN    │  PAIN    │  PAIN    │  PAIN    │  PAIN    │
│ POINTS   │ POINTS   │ POINTS   │ POINTS   │ POINTS   │
├──────────┼──────────┼──────────┼──────────┼──────────┤
│  OPPS    │  OPPS    │  OPPS    │  OPPS    │  OPPS    │
│(needs)   │(needs)   │(needs)   │(needs)   │(needs)   │
└──────────┴──────────┴──────────┴──────────┴──────────┘

Row 1 -- Doing (Actions): What the customer physically does at this step. Be specific: "Opens three browser tabs to compare prices" not "Researches options."

Row 2 -- Thinking (Questions & Goals): What the customer is trying to figure out or decide. "Am I getting a good deal?" "Is this the right size?" "What do other people recommend?"

Row 3 -- Feeling (Emotions): The emotional state at this step. Use specific emotion words: frustrated, anxious, confident, overwhelmed, relieved, excited, bored.

Row 4 -- Pain Points: Where the experience breaks down. Long waits, confusing interfaces, missing information, forced workarounds, dead ends.

Row 5 -- Opportunities: Customer needs that emerge from the pain points and emotions. These feed directly into the OST.

How to Build an Experience Map

Step 1: Choose the Experience to Map

Select a specific goal that your target customers are trying to accomplish. The scope should be:

• Broad enough to capture the full experience (not just the part involving your product)
• Narrow enough to be mappable in a single session (not "manage their entire business")

Too Broad	Too Narrow	Just Right
"Manage finances"	"Click the save button"	"Prepare and file quarterly taxes"
"Do marketing"	"Write an email subject line"	"Plan and execute a product launch campaign"
"Stay healthy"	"Log a meal"	"Decide what to eat for a healthy weeknight dinner"

Step 2: Gather the Data

Experience maps must be built from real customer data, not team assumptions. Sources include:

Source	What It Provides	How to Use
Interview snapshots	Specific stories about how customers accomplish the goal	Extract steps, emotions, and pain points from stories
Support tickets	Common failure points and confusion	Map where in the experience breakdowns occur
Analytics / session recordings	What users actually do in your product	Validate or challenge interview findings
Contextual inquiry	Direct observation of users in their environment	Capture steps that users don't think to mention

Minimum data: At least 5 interview snapshots describing the same general experience before attempting to map it. Fewer than 5 and the map will reflect individual stories, not patterns.

Step 3: Map the Steps

Lay out the major steps of the experience from beginning to end. Start rough and refine.

Process:

1. Review interview snapshots and list every distinct step mentioned
2. Arrange steps in chronological order
3. Merge similar steps described by different participants
4. Add steps that participants implied but didn't explicitly state
5. Validate the sequence: does this flow make sense?

Example -- "Hiring a contractor for home renovation":

1. Realize renovation is needed
2. Research what's involved and set a budget
3. Ask friends and search online for contractors
4. Contact 3-5 contractors for estimates
5. Compare estimates and check references
6. Select a contractor and negotiate terms
7. Manage the project during renovation
8. Inspect and approve the finished work
9. Handle issues or follow-up repairs

Step 4: Fill In the Rows

For each step, use interview data to populate the Doing, Thinking, Feeling, and Pain Point rows.

Example -- Step 4: "Contact 3-5 contractors for estimates":

• Doing: Calling phone numbers, leaving voicemails, sending emails, filling out contact forms on websites
• Thinking: "How many should I contact?" "What should I ask?" "How do I compare their responses?"
• Feeling: Anxious about making the right choice, frustrated when calls go to voicemail, overwhelmed by different formats of estimates
• Pain Points: Many contractors don't call back; estimates come in different formats making comparison difficult; no standard way to evaluate quality

Step 5: Identify Opportunities

Review each pain point and emotion peak on the map and translate them into opportunity statements for the OST.

Translation examples:

Pain Point	Opportunity Statement
Estimates come in different formats	"Homeowners need a way to compare contractor estimates on an apples-to-apples basis"
Many contractors don't call back	"Homeowners need a reliable way to reach responsive contractors"
Overwhelmed by different options	"Homeowners need guidance on what criteria matter most for their specific project"

Collaborative Mapping Exercises

The Workshop Format (2-3 Hours)

Experience maps are most valuable when built collaboratively by the product trio. The exercise creates shared understanding that no document can replicate.

Participants: Product manager, designer, engineer(s), and optionally: data analyst, customer success representative

Materials: Large wall or digital whiteboard, sticky notes (physical or virtual), markers, printed interview snapshots

Agenda:

Time	Activity	Purpose
0-15 min	Review the goal and scope of the experience to map	Align on boundaries
15-45 min	Individual review: each person reads 3-5 snapshots and writes steps on stickies	Gather diverse perspectives
45-75 min	Collaborative arrangement: place steps on the wall, discuss sequence, merge duplicates	Build shared timeline
75-105 min	Fill in rows: add Doing, Thinking, Feeling, Pain Points for each step	Deepen understanding
105-135 min	Identify opportunities: translate pain points into opportunity statements	Connect to the OST
135-150 min	Prioritize: which opportunities are most impactful and best supported by evidence?	Focus the team

Facilitation Tips

• Start with divergence: Let each person work independently before coming together, to avoid groupthink
• Use quotes: Place verbatim customer quotes on the map to keep it grounded
• Mark confidence levels: Use dots or colors to indicate which steps are well-supported by evidence (green) vs. assumed (red)
• Capture disagreements: When team members see the experience differently, that's valuable -- it reveals where you need more data
• Time-box ruthlessly: It's better to have a rough complete map than a detailed partial one

Remote Collaboration

For distributed teams, use digital whiteboarding tools (Miro, FigJam, Mural) with these adaptations:

• Pre-populate the template before the session
• Use breakout rooms for the individual review phase
• Assign a facilitator to manage the digital board and prevent chaos
• Record the session for team members who can't attend

Using Maps to Generate Opportunities

The Opportunity Extraction Process

After the map is built, systematically scan it for opportunities:

1. Emotion peaks: Where do feelings become strongly negative (frustrated, anxious, overwhelmed) or surprisingly positive (relieved, delighted)? Negative peaks are unmet needs; positive peaks are moments to protect or amplify.

2. Workarounds: Where are customers cobbling together multiple tools, doing manual work, or inventing their own solutions? Workarounds signal high-value unmet needs -- the customer is already motivated enough to create their own solution.

3. Drop-off points: Where do customers abandon the experience or give up? These are the highest-friction moments and represent either simplification opportunities or entirely new approaches.

4. Handoff points: Where does the customer move from one tool, person, or context to another? Handoffs create information loss, confusion, and frustration.

5. Wait times: Where does the customer have to wait -- for information, for another person, for a process to complete? Waiting creates anxiety and abandonment.

Opportunity Quality Check

For each opportunity extracted from the map, verify:

Check	Question	If No
Customer-framed	Is this stated from the customer's perspective?	Rewrite: "Users need..." not "We should build..."
Evidence-based	Is this supported by at least 2-3 interview stories?	Flag as hypothesis; gather more evidence
Solution-agnostic	Does this describe a need without prescribing a solution?	Remove the implied solution; focus on the need
Actionable scope	Is this specific enough to generate solution ideas?	Break into sub-opportunities

Maintaining Maps Over Time

Experience maps are living documents that should evolve as the team conducts more interviews and the product changes.

Update Triggers

Trigger	What to Update
New interview reveals a step you missed	Add the step and associated rows
Multiple interviews contradict a step on the map	Revise the step or split into segments
Your product changes the experience	Update affected steps; look for new pain points
A competitor enters the space	Map how the experience changes with the competitor's solution
You expand to a new customer segment	Create a parallel map for the new segment; compare

When to Create a New Map vs. Update an Existing One

• Update when the goal is the same but details have changed
• Create new when you're exploring a different goal or a significantly different customer segment
• Archive old maps rather than deleting them -- they provide historical context

Example: Complete Experience Map

Experience: "Small business owner creating and sending an invoice"

Step 1 -- Complete the work

• Doing: Finishing the project, tracking hours, gathering receipts
• Thinking: "Did I track everything? Am I forgetting any billable items?"
• Feeling: Relieved work is done, anxious about accuracy
• Pain: No single place where all billable items live; have to check email, time tracker, and notes

Step 2 -- Create the invoice

• Doing: Opening invoicing tool, entering line items, adding client details
• Thinking: "What's the right format? Do I need a PO number? What's the tax rate?"
• Feeling: Tedious, worried about looking professional
• Pain: Re-entering information that exists elsewhere; unsure about tax rules

Step 3 -- Review and send

• Doing: Proofreading, saving as PDF, attaching to email, writing a message
• Thinking: "Does this look professional? Will they pay on time?"
• Feeling: Anxious about the payment timeline, insecure about professionalism
• Pain: Manual process of export-attach-email; no tracking of whether client received it

Step 4 -- Wait for payment

• Doing: Checking bank account, checking email for confirmation
• Thinking: "Did they get it? Should I follow up? When is it rude to ask?"
• Feeling: Anxious, uncertain, sometimes resentful
• Pain: No visibility into whether invoice was viewed; unclear payment timeline

Step 5 -- Follow up on late payment

• Doing: Writing a follow-up email, calling the client, feeling awkward
• Thinking: "How do I ask without damaging the relationship?"
• Feeling: Frustrated, uncomfortable, dreading the conversation
• Pain: No standard follow-up process; feels personal rather than professional

Opportunities extracted:

1. "Business owners need all billable items in one place so nothing falls through the cracks"
2. "Business owners need to create professional invoices without re-entering data they've already recorded"
3. "Business owners need visibility into whether a client has seen an invoice"
4. "Business owners need a way to follow up on late payments that feels professional, not personal"
5. "Business owners need clarity on tax rules relevant to their specific invoices"