liveBook · Manning

Customer journey

As explained in Design for Developers

A user journey map is a visual narrative of a user's actions, thoughts, feelings, and opportunities for improvement across connected product touchpoints.

A customer journey map is a visual narrative of one target user’s experience across connected product touchpoints. It follows what the person does, thinks, and feels while pursuing a specific goal, then turns positive and negative moments into opportunities for improvement. Unlike a user flow, which clarifies task steps, a journey adds context and emotion. section 5.2 section 5.2.2

Build a useful journey map by narrowing the perspective and connecting actions to experience:

  • Choose one target user persona rather than combining audiences with different behaviors. section 5.2.2
  • Define a specific scenario, goal, or task, and limit its scope so the map produces focused insights. section 5.2.2
  • Map each scenario step to what the user may be thinking, doing, or feeling, including positive and negative moments. section 5.2.2
  • Identify opportunities to improve the experience, using user research to avoid assumptions about the user’s point of view. section 5.2 section 5.2.2
  • Include relevant digital and physical touchpoints when the experience crosses between spaces. section 5.2.2

Booking a train ticket

A journey map can follow one person booking a train ticket through an app, recording each stage of the scenario alongside the person’s actions, thoughts, feelings, and improvement opportunities. A healthcare journey might similarly connect a website visit with the physical experience of visiting a provider. section 5.2.2

Figure 5.7 A simple user journey map that depicts the scenario of a user booking a train ticket and their experience with the app. User journey maps can be created with tools such as Figma, Illustrator, or even Microsoft Word.

Inspect a simple journey map for booking a train ticket; journey maps can be created in Figma, Illustrator, or Microsoft Word. section 5.2.2

How Design for Developers covers it

How deep it goes
Defines persona, scope, steps, thoughts, feelings, and opportunities, while stopping short of implementation detail.
Examples
Uses a train-ticket booking app and a healthcare experience spanning a website and provider visit.
What it assumes
Builds on site maps, information architecture, and user research while distinguishing journeys from task-focused user flows.
What you can do after
Apply it to map a focused persona scenario and identify experience improvements from observed emotional moments.
How it connects
Connects user flows, user research, user personas, touchpoints, information architecture, wireframes, and prototyping.

Also explained in

Compare how 6 books explain customer journey →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Design for Developers. The section links point to the parts of the book it draws on.