methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session2-4 hWorkshopJourney Map

Session: Customer Journey Mapping

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 4-10. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Journey Map. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 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"). Hint: If start or end is unclear, the map becomes endless or too short. Scope is mandatory.

    FacilitatorJourney Map
  2. 2

    Phase 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). Hint: Classic funnel stages (awareness, consideration) are often wrong. Better phases from customer perspective such as "searching for solution", "comparing", "first use".

    FacilitatorPain-point List
  3. 3

    Phase 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. Hint: Stickies should be verb phrases ("searches comparison portal", "reads reviews"). Nouns without action are too vague.

    FacilitatorOpportunity Backlog
  4. 4

    Phase 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. Hint: 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.

    FacilitatorJourney Map
  5. 5

    Phase 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. Hint: Opportunities are not solutions. Better to say "reduce friction at login" than "introduce SSO". Solution selection comes in the next step.

    FacilitatorPain-point List
  6. 6

    Phase 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. Hint: A map without follow-up sinks in the wiki. At least three opportunities need owner and deadline before workshop end.

    OwnerOpportunity Backlog
  7. 7

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerJourney Map
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Customer Journey Mapping

Goal

Artifact: Journey Map

Working Question

How does the selected persona experience the end-to-end journey, where does friction or frustration occur, and what opportunities emerge from these gaps?

Context

Interview highlights with quotes; selected persona or segment; current touchpoint overview (CRM, app, hotline, branch); known pain points from support tickets or complaints.

Setup

  • Format: Method session
  • Duration: 2-4 h
  • Mode: Workshop
  • Participants: 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.
  • Owner: One UX researcher or service designer as facilitator
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Journey Map. After the session, the artifact should be shareable, reviewable, or reusable.

Input

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.

Preparation

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.

Agenda

  1. Phase 1: Define persona and scope (15 min) Owner: Facilitator Action: 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"). Hint: If start or end is unclear, the map becomes endless or too short. Scope is mandatory. Output: Journey Map

  2. Phase 2: Map phases (20-30 min) Owner: Facilitator Action: Identify 4-7 main phases with a persona perspective. Do not use company funnel stages, use customer perspective (what the customer does and feels). Hint: Classic funnel stages (awareness, consideration) are often wrong. Better phases from customer perspective such as "searching for solution", "comparing", "first use". Output: Pain-point List

  3. Phase 3: Actions and touchpoints (30-45 min) Owner: Facilitator Action: 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. Hint: Stickies should be verb phrases ("searches comparison portal", "reads reviews"). Nouns without action are too vague. Output: Opportunity Backlog

  4. Phase 4: Emotions and pain points (30-45 min) Owner: Facilitator Action: 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. Hint: 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. Output: Journey Map

  5. Phase 5: Opportunities and prioritization (30-45 min) Owner: Facilitator Action: 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. Hint: Opportunities are not solutions. Better to say "reduce friction at login" than "introduce SSO". Solution selection comes in the next step. Output: Pain-point List

  6. Phase 6: Snapshot and follow-up (10 min) Owner: Owner Action: Capture photo or digital export. Add persona and date to map. Move top opportunities into backlog with owner and due date. Hint: A map without follow-up sinks in the wiki. At least three opportunities need owner and deadline before workshop end. Output: Opportunity Backlog

  7. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Journey Map

Closeout

  • Update result artifact: Journey Map
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Journey Map: Customer Journey Mapping

Working Question

How does the selected persona experience the end-to-end journey, where does friction or frustration occur, and what opportunities emerge from these gaps?

Context

Interview highlights with quotes; selected persona or segment; current touchpoint overview (CRM, app, hotline, branch); known pain points from support tickets or complaints.

Participants

  • Owner: One UX researcher or service designer as facilitator
  • Participants: 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.

Input

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.

Template

Customer Journey Mapping Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Journey Map:
  • Pain-point List:
  • Opportunity Backlog:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Journey Map is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Customer Journey Mapping Working Template

View templateCompact working template for Customer Journey Mapping with context, input, output artifacts, and next step.
canvas

journey-map-working-template.md

Compact working template for Customer Journey Mapping with context, input, output artifacts, and next step.

Customer Journey Mapping Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Journey Map:
  • Pain-point List:
  • Opportunity Backlog:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Journey Map.
  • 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.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.