startthat.work home

AO-05 Customer journey mapping

Turns a persona goals, actions, thoughts and emotions across stages into a visual map, producing a map with phases, touchpoints, pain points and opportunities.

Assess actors, options and risksEvidence: DocumentedPrimary technique, runs in step 5.3Strongest statement: describe

What it does

Turns a persona's goals, actions, thoughts and emotions across stages into a visual to find friction. Artefact: a map with phases, touchpoints, pain points and opportunities.

When to use it

Use when a user asks where customers meet friction in a service, or wants to see an experience from the customer side stage by stage.

When it does not fit

The map is drawn before the research is synthesised, which produces attractive but flawed maps; one persona per basic map.

Result format

The result is a map for one persona with the stages as columns and rows for touchpoints, actions, thoughts and emotions. It marks the pain points at each phase and ends with a list of opportunities.

Requirements on the material

PropertyRequirement typeRequirement
Content typeAlways appliesrequires=text
Unit of analysisAlways appliesrequires=topic
Appraises source credibilityApplies in some casesno

Not restricted on: Structure, Variable types, Time structure, How the sample was chosen, Level of detail available, Number of sources, Whether sources can be joined, Amount of material, Known data problems, Producer interest, Source dependence, Origin, Document genre, Language, Personal information, Security classification, Licence.

Minimum materialExisting research synthesised first, then field research that follows the customer stages; one persona for each basic map. Quantitative data cannot build the story alone.
Additional sources needednone
Not for (rules)none
Not for (text)Wrong choice when the map would be drawn before the research is synthesised, which gives attractive but flawed maps, or when several personas are merged into one map.

Choosing and ordering

Kind of techniquePrimary technique, runs in step 5.3
Phase taganalyse
Other phase tagsreport
Kind of findinggap; pattern
Question answeredwhat; why
Strongest statement it supportsdescribe
Needs as input
Makes as output
Must exist firstNone
Loop targetreturn to gather

Library checks by stakes

Each stakes level includes the checks of the level below it. Checks that need a person apply at high stakes only, so the process leaves them out at lower stakes (decision 38). Repeatability: judgement dependent.

StakesCheckPerson involvedCounts as a different method
exploratoryassumption and limitation statementnoneno
decision-informingassumption and limitation statementnoneno
decision-informingsource-span citationnoneno
decision-informinghuman review sampleneeded; left out below high stakesno
high-stakesassumption and limitation statementnoneno
high-stakessource-span citationnoneno
high-stakeshuman review sampleneededno
high-stakesindependent reviewneededno
high-stakesexpert reviewneededno

Failure modes and limits

Model suitabilityhuman judgement required
Typical model failureDraws an attractive map from assumptions before the research is synthesised, and merges several personas into one.
Error sourcesinput data; source selection; coder or rater judgement; language model
Certainty limitsCertainty drops when the map rests on assumptions, not field research (risk of bias), and when one persona stands for varied customers (indirectness).

Evidence and tag basis

Documented. Documented by a user-research consultancy. (Nielsen Norman Group, Customer journey mapping)

Tag basis: input profile inference; selection inference; sequencing inference; robustness inference. All tag values are inference unless a source is named.