User Journey Map

Anyone who uses an app or a website rarely does so in a single step. You become aware of something, search for information, try it out, decide, and keep using it. A user journey map writes down exactly this sequence, usually as a timeline running from left to right. Underneath each step comes what the person is doing at that moment, what they want to achieve, and how satisfied or annoyed they are. The result is not a statistic but a kind of map of the experience a person has with an offering. Companies use it to understand at which point they lose users.

Why companies lose sight of their users

In larger companies, each department works only on its own slice. Marketing takes care of the advertising, developers take care of the app, customer service takes care of complaints. Each department considers its part to be good. Nevertheless, the overall experience can be poor because no one looks at it as a whole.

One example: an advertisement promises sign-up in thirty seconds. The form then, however, demands a phone number and confirmation by mail. Both departments have done their own work cleanly. The user still drops out. A journey map makes such breaks between areas of responsibility visible.

The second benefit is economic. Every step at which many people give up directly costs money. If an online shop knows that half of all buyers abandon the process at checkout, it also knows where an improvement would pay off the most. Without this overview, people often improve things that already work fine anyway.

What such a map consists of

At the start there is a persona. This is a fictional but typical example person with a name, age, and goals. It replaces the vague term “the user” with someone concrete. For students and for retirees, the paths through the same app often look completely different, which is why several personas are usually needed.

After that, the process is divided into phases, such as becoming aware, comparing, buying, using, seeking help. In each phase, one notes the touchpoints, meaning all points of contact with the company: an ad, an email, a button, a phone call with support. Below that comes a row for thoughts and one for mood, often drawn as a rising and falling line.

What matters is where the information comes from. A good journey map is based on interviews, observations, and usage data from the app. A bad one arises in a meeting where a team guesses how customers probably feel. The most common mistake is to treat the map as a finished result. It is a working tool and becomes outdated as soon as the product changes.

From the design agency to the chatbot

Journey maps originally come from marketing and interface design. Today they hang on the wall in almost every product department or live in programs like Figma and Miro. Banks, insurance companies, and government agencies also use them to simplify application procedures.

In the AI industry, the term appears from two directions. First, journey maps are increasingly generated from real data instead of being drawn by hand: software analyzes click paths and shows the most common routes through a product. Second, they are used to plan at which point a chatbot or an assistant is actually genuinely helpful. Not every step is improved by automation; some users want to speak to a human at sensitive points.

The term should be distinguished from the funnel. A funnel shows only sober numbers: how many people move from step one to step two. The journey map adds the question of why they drop out. In job postings for UX design and product management, it is therefore considered a standard tool.