A user journey map shows a product not as a set of screens, but as a sequence of decisions, expectations, and barriers. It is especially useful for mobile journeys, where people interrupt actions, switch apps, or work on unstable networks.

What belongs on the map

  • The user’s goal before opening the app.
  • Steps and decision points.
  • Questions, doubts, and emotions at each stage.
  • Data the system needs and errors that can occur.
  • The expected outcome and next step.

Do not build the map only from internal assumptions. Combine analytics with interviews, session recordings, support data, and observation. The YouTube Go story shows how field context can change the presentation of a feature: when people do not understand data costs, the product should show that cost before playback.

Turning a map into decisions

Mark the highest-risk points and choose one barrier to investigate. Do not try to fix the entire journey at once. For every change, define an event that can show improvement: completed steps, fewer retries, or faster access to the outcome.

A journey map is not a one-time document. Update it after major releases, audience changes, or a new acquisition channel. A living map gives design, engineering, marketing, and support a shared view of the experience.

Source: Google Design: Making YouTube Go.