RunsheetUX Design

Customer Journey Canvas

ComplexityMedium

Time1-3 h

Participants3-10

FormatWorkshop

MaturityEstablished

Prerequisite

What needs to be finished first

Complete firstPersona or segment

A concrete persona with goals, context, and starting situation is defined, and the canvas applies to it.

Without: Without a persona anchor the canvas becomes generalized and produces no actionable opportunities.

Complete firstCustomer research

Research notes, interview highlights, or service data for the selected Customer Journey are available.

Without: Without research, the canvas is filled with internal assumptions and reflects the organization's wish list.

Preparation

What needs to be ready before start

Materials

Customer-journey canvas template (for example Design a Better Business) with columns for phases, rows for Customer Doing, Touchpoints, Customer Thinking & Feeling, Pain Points, Opportunities; stickies; markers; research notes ready.

People / roles

A service designer or UX researcher as facilitator; persona owner from research; 3-7 stakeholders from Product, Service, Marketing, Operations; one note-taker.

Pre-read

Persona profile; research highlights and quotes; current touchpoint list; known pain points from support or NPS; scope definition (start and end of the journey).

Time needed

1-3 h

Setup

Post the canvas in working space and place persona at the top. Pre-label phase columns (or leave empty for co-definition). Define sticky colors per row. Set timer to 90 min.

Core question

The one question this method answers

How does the persona experience the journey end-to-end, at which touchpoints, with which emotions, and where are concrete improvement opportunities?

Flow

Marker: Phase

Step	Duration	Action	Hint
1Phase 1: Persona briefing	10 min	Present persona profile: goals, context, current situation. Define journey scope (trigger and endpoint). Build shared understanding before adding content.	If the team does not share the persona, the canvas becomes inconsistent. Align persona first, then map.
2Phase 2: Phases and customer doing	20-30 min	Define 4-7 phases from persona perspective. Collect key customer actions per phase as verb-style stickies. Base on research notes.	Actions are what the persona does, not what we offer. The distinction matters: "reads reviews" versus "receives newsletter."
3Phase 3: Touchpoints and channels	15-20 min	For each action, define touchpoint and channel (App screen, hotline number, office XY). Mark cross-channel transitions.	Gaps between channels (for example app to hotline) are often key pain points. Mark transitions explicitly.
4Phase 4: Customer thinking & feeling	20-30 min	Capture emotional state and thoughts for each phase (for example "uncertain," "relieved," "lost"). Support with interview quotes. Draw an emotion curve across all phases.	Overly positive emotion curves (all upward) are warning signs. Real journeys have emotional dips. Use real quotes for grounding.
5Phase 5: Pain points and opportunities	20-30 min	Mark pain points as red stickies, opportunities as green. Opportunity describes the problem space, not solution. Mark top three opportunities with owner.	Pain points without opportunity are complaints. Opportunity without pain is a wish. Explicitly connect the two.
6Phase 6: Synthesis and follow-up	10-15 min	Photograph or export the canvas. Move top three opportunities with owner and date into backlog. Plan follow-up workshops (Service Blueprint, Solution Sprint).	Without follow-up, the canvas drifts away. At least three opportunities need owners by end of workshop.

Artifact

What comes out at the end

Form

Customer Journey Canvas (image or export) with persona, phases, Customer Doing, Touchpoints, Thinking & Feeling with emotion curve, Pain Points and Opportunities; plus opportunity backlog with owner, prioritization, and follow-up date.

Versioning / ownership

One canvas per persona with date. For implementation iterations create a new version and keep old one. Document before/after comparison in a separate file.

Tool alternatives

Miro or FigJam with journey canvas template
Smaply as specialized tool
UXPressia for persona-integrated canvases
Mural with journey template
A1 print with stickies and photo export

customer-journey-canvas-working-template.md

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

Customer Journey Canvas 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

Customer Journey Canvas:
Pain Points:
Experience Opportunities:

Open questions

Next step

Owner, date, success signal.

Example output

Concrete filled scenario, fictional example

customer-journey-canvas-beispiel.md

Concrete filled scenario, fictional example

Customer Journey Canvas — Persona "Sabine" (Freelance tax advisor, v1 2026-05-18)

Persona summary: 47 years old, solo, 65 clients, DATEV veteran, seeking an alternative after data loss.

Scope: "first search" to "first successful VAT return submission"

Phases

1. Trigger: data loss -> urgent search

Doing: Googles alternatives, asks colleagues
Touchpoints: Google, forum, personal network
Feeling: angry, driven, skeptical ("Who can be trusted?")
Pain: trust is lost, each solution seems risky
Opportunity: trust signals on landing page ("99.99% uptime", audit trail)

2. Research: compares 3-5 options

Doing: reads comparison articles, watches YouTube demos, checks pricing
Touchpoints: comparison portals, own website, demo videos
Feeling: overwhelmed, comparing apples and oranges
Pain: marketing language does not help, DATEV compatibility is hidden
Opportunity: DATEV comparison as headline, not in feature list

3. Demo test: tries top-2 candidates

Doing: opens demo account, tests first documents
Touchpoints: demo account, onboarding wizard
Feeling: quickly impatient (30 min test rule)
Pain: if DATEV export is not found within 10 min, they drop out
Opportunity: DATEV export as first tutorial step

4. Purchase: selects provider and activates subscription

Doing: plan choice, payment input, first client migration
Touchpoints: pricing page, checkout, migration assistant
Feeling: relieved after decision, still anxious about migration
Pain: unclear per-customer pricing, migration without guidance
Opportunity: 30-minute onboarding call included

5. First usage: submits first VAT return

Doing: submits quarterly return in new software
Feeling: tense, then relieved if it works
Pain: no VAT code help, error messages are technical
Opportunity: inline help for VAT-code support

Top-3 opportunities (prioritized)

Increase DATEV visibility in demo flow (Owner: @anna, Q3 2026)
30-minute onboarding call plus subscription (Owner: @marcus, Q3 2026)
Inline VAT code help in first-time flows (Owner: @ben, Q4 2026)

What to do

Complete As-Is fully first, then sketch To-Be separately (second canvas). Mixing confuses and hides trade-offs.

Stop criteria

Done signals checkable in under a minute

No persona or segment defined.

No research notes are available; canvas would be guesswork.

Journey scope is not bounded and the canvas becomes endless.

Touchpoints in the organization are unknown, so findings lack reliability.

Stakeholder demands internal process optimization, Service Blueprint fits better.

No willingness to follow up, canvas disappears into wiki.

Finished the runsheet?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profile More methods