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.
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
| Property | Requirement type | Requirement |
|---|---|---|
| Content type | Always applies | requires=text |
| Unit of analysis | Always applies | requires=topic |
| Appraises source credibility | Applies in some cases | no |
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 material | Existing 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 needed | none |
| 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 technique | Primary technique, runs in step 5.3 |
|---|---|
| Phase tag | analyse |
| Other phase tags | report |
| Kind of finding | gap; pattern |
| Question answered | what; why |
| Strongest statement it supports | describe |
| Needs as input |
|
| Makes as output |
|
| Must exist first | None |
| Loop target | return 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.
| Stakes | Check | Person involved | Counts as a different method |
|---|---|---|---|
| exploratory | assumption and limitation statement | none | no |
| decision-informing | assumption and limitation statement | none | no |
| decision-informing | source-span citation | none | no |
| decision-informing | human review sample | needed; left out below high stakes | no |
| high-stakes | assumption and limitation statement | none | no |
| high-stakes | source-span citation | none | no |
| high-stakes | human review sample | needed | no |
| high-stakes | independent review | needed | no |
| high-stakes | expert review | needed | no |
Failure modes and limits
| Model suitability | human judgement required |
|---|---|
| Typical model failure | Draws an attractive map from assumptions before the research is synthesised, and merges several personas into one. |
| Error sources | input data; source selection; coder or rater judgement; language model |
| Certainty limits | Certainty drops when the map rests on assumptions, not field research (risk of bias), and when one persona stands for varied customers (indirectness). |
Related techniques
- should follow AO-06 Personas: a persona grounded in research gives the single actor for the map
- pairs with AO-07 Jobs to be done (JTBD): a job statement explains why a stage matters to the customer
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.