In UX design, what does a customer journey map show that a persona does not, and which layers does it typically contain?

## What a journey map adds A **persona** describes who a user is; it has no sense of time. A **customer journey map** adds the time axis: it follows one person through a scenario from the first trigger to the outcome and shows how the experience unfolds, where it breaks, and how it feels at each point. Its purpose is to give a team — often spanning product, engineering, support and hardware — one shared picture of an end-to-end experience that no single team owns. ## The lens: one persona, one scenario Every useful map starts by fixing its **lens**: - **who** — one persona or segment; - **which scenario** — a concrete situation with a goal, such as “set up a new smart thermostat until the first heating schedule runs by itself”; - **expectations** — what the person expects to happen, which later explains the emotional dips. Mixing several personas or scenarios on one map averages their experiences together, and the pain points that matter to one group disappear under the others. ## The layers | Layer | What it records | Thermostat setup example | |---|---|---| | Stages | The high-level phases of the scenario | Unbox, install, pair, configure, first week | | Actions | What the person does in each stage | Turns off power, reads the wiring guide, scans the device code | | Touchpoints | Every place the person meets the product or company | Packaging, printed guide, indicator light, app, support chat | | Thoughts | Questions and beliefs at each moment | “Is this wire the right one?” | | Emotions | A curve of how the experience feels | Excited, anxious, frustrated at pairing, relieved | | Pain points | Where friction or failure occurs | Pairing times out with no explanation | | Opportunities | What the team could change | Show pairing progress on the device itself | Some maps add **ownership** — which team owns each touchpoint — and **metrics** such as drop-off or support contacts per stage, which turn the map into a prioritisation tool. ## Touchpoints beyond the screen A smart-home product shows why touchpoints must include more than the app. The person meets the product through the box, a printed guide, the device's indicator light, the home network, perhaps an installer, customer support, a household member who was never asked, and the app on a phone or a wall panel. Many of the sharpest pain points sit **between** channels — the app says “waiting for device” while the device shows a light pattern nobody explained. A map that lists only app screens hides exactly those seams. ## Current-state and future-state maps - A **current-state** map documents today's experience. It must be grounded in research — observation, interviews, support logs, analytics — or it maps the team's assumptions instead. - A **future-state** map describes the experience the team intends to create. It is a design vision and should be labelled as one. - A common sequence is to build the current state, prioritise its pain points, then design the future state and trace which change addresses which pain point. ## How to keep a journey map grounded 1. **Source every pain point** — a quote, an observation, a support-ticket count. 2. **Plot emotions from evidence**, not from what the team imagines a step feels like. 3. **Mark assumptions** visibly wherever research is thin. 4. **Quantify where possible**: drop-off at each stage, support contacts per stage. 5. **Revisit** when the product or channel mix changes; a map of last year's setup flow misleads. ## Neighbouring artefacts - A **service blueprint** extends the journey downward into what the organisation does behind each touchpoint — frontstage staff, backstage processes, supporting systems. - A **user flow** diagrams the screens and decisions inside one product task; it is narrower and carries no emotion layer. - An **empathy map** is a snapshot of mindset with no sequence at all. Knowing which of these a question calls for is part of the skill: a journey map answers “where and why does the end-to-end experience hurt?”, not “which screen comes next?”.