What needs to be finished first
5-10 recent interviews or observations with target users are available, with actions, emotions, and pain points supportable with quotes.
A concrete persona or clearly delimited segment is selected, and the journey applies to it (one map per persona).
What needs to be ready before start
Large whiteboard or digital board (Miro, FigJam, Mural); journey map template with columns for phases and rows for actions, touchpoints, emotions, pain points, opportunities; sticky notes in colors per row; markers.
One UX researcher or service designer as facilitator; 3-7 stakeholders from product, service, and operations; at least one researcher with direct customer contact; one note-taker for opportunities.
Interview highlights with quotes; selected persona or segment; current touchpoint overview (CRM, app, hotline, branch); known pain points from support tickets or complaints.
2-4 h
Board with columns for 4-7 phases (for example awareness, consideration, purchase, onboarding, use, retention). Prepare rows: Customer Action, Touchpoint, Channel, Emotion (smileys or line), Pain Points (red), Opportunities (green). Pin persona at top.
The one question this method answers
How does the selected persona experience the end-to-end journey, where does friction or frustration occur, and what opportunities emerge from these gaps?
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Define persona and scope | 15 min | Pin persona card with name, role, context, and journey goal at the top. Formulate scope of the journey (start and end) as one sentence (for example "From first Google search to first re-order"). | If start or end is unclear, the map becomes endless or too short. Scope is mandatory. |
2Phase 2: Map phases | 20-30 min | Identify 4-7 main phases with a persona perspective. Do not use company funnel stages, use customer perspective (what the customer does and feels). | Classic funnel stages (awareness, consideration) are often wrong. Better phases from customer perspective such as "searching for solution", "comparing", "first use". |
3Phase 3: Actions and touchpoints | 30-45 min | Per phase: which concrete actions does the persona take? Which touchpoints (website, app, email, hotline, branch) does it interact with? Which channels are used? Derive this from interview data, do not invent. | Stickies should be verb phrases ("searches comparison portal", "reads reviews"). Nouns without action are too vague. |
4Phase 4: Emotions and pain points | 30-45 min | For each action: mark emotional state on a scale (very positive to very negative) with quote evidence when available. Mark pain points in red; one short sentence per pain. | If the emotional line stays flat or only slightly negative across the entire journey, it is whitewashed or not research-based. Real journeys have dips. |
5Phase 5: Opportunities and prioritization | 30-45 min | For each pain point or deep emotional dip, add opportunity stickies (green): how can friction be reduced? Prioritize top 5 opportunities (impact × feasibility). Include owner and next action per top opportunity. | Opportunities are not solutions. Better to say "reduce friction at login" than "introduce SSO". Solution selection comes in the next step. |
6Phase 6: Snapshot and follow-up | 10 min | Capture photo or digital export. Add persona and date to map. Move top opportunities into backlog with owner and due date. | A map without follow-up sinks in the wiki. At least three opportunities need owner and deadline before workshop end. |
What comes out at the end
Customer Journey Map (image or digital export) with persona, phases, actions, touchpoints, emotions, pain points, and opportunities, plus an opportunity backlog with owner, prioritization, and follow-up date for each top item.
One map per persona. When iterating (for example after implementations), create a new dated version. Document before/after comparison explicitly. Refresh map as living artifact every 6-12 months.
Compact working template for Customer Journey Mapping with context, input, output artifacts, and next step.
What is this method used for?
Which question should be answered at the end?
Which data, observations, or materials are available?
Owner, date, success signal.
Concrete filled scenario, fictional example
Concrete filled scenario, fictional example
Persona: Sabine, 47, solo tax advisor with 65 clients, using DATEV for 12 years Scope: From "searching for new bookkeeping solution" to "successful quarterly VAT filing in new software"
1. Trigger (Pain: 8/10)
2. Research (Emotion: slightly negative, mixed)
3. Demo / trial (Emotion: skeptical to critical)
4. Decision (Emotion: critically positive)
5. First quarterly use (Emotion: stressed -> relieved)
Recognize symptoms and steer against them
The workshop creates the journey without interview data or observations.
Require research synthesis before workshop. In workshop, ask for quotes per pain point. If no evidence exists, mark it as assumption and plan follow-up research.
The map covers multiple personas and becomes an average with low decision value.
One map per persona. For several important personas, use multiple maps side-by-side, not a mixed one.
Phases are awareness/consideration/purchase from company view, not customer view.
Use customer-verb phases ("searching", "comparing", "trying"). If a phase is a marketing term, it is wrong.
Emotional line stays flat or only slightly negative, without depth.
Ask explicitly for frustration, escalations, and workarounds at each phase. Real journeys have depth; without depth there are no insights.
Opportunity column contains finished feature ideas rather than problem spaces.
Frame opportunities as problem statements ("reduce friction at login"), and derive solutions in a separate backlog session.
Done signals checkable in under a minute
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.