Customer journey and scenarios

Customer journeys describe the path to a goal through channels and time, not just a sequence of product screens: Build a map for a specific segment and situation, back up milestones with research and data, and mark points where the problem is both user-relevant and team-driven.

Basis for UX and Experience Management

What is a customer journey?

Definition

Customer journey is the entire sequence of interactions between a person and a product, from the first thought of a task to the moment when their expectations are met or they leave. It’s not just a map of screens or processes within an application; it includes external triggers, contexts, emotions, pain points and moments of joy.

Example

The way to order a taxi: first, the user has a need (to go to a meeting), then he chooses an application, logs in, chooses a route, confirms the order, goes, evaluates the trip. At each stage, something can go wrong. For example, the user loses the session and is forced to re-enter, this immediately worsens the impression and affects loyalty.

Typical errors

The main mistake is to draw a customer journey solely by technical process, a trap for teams that do not communicate with real users and do not take into account the context, another mistake is to think only about the interface, forgetting about offline stages or third-party services (for example, email, contact center, bank payment).

Scripts are key building blocks of the user journey

Definition and distinction

The script is the specific situation of a product being used: what, where and why the user is doing, and in practice, the scripts answer three questions: why the person came, how they act, and what the outcome will be.

Scenarios are different from features and features in a product: one function can occur in different scenarios, and vice versa - one scenario can be implemented by different features.

Case.

In online banking, a script: a user wants to quickly transfer money to a friend. Although the function is to transfer funds, the purpose of the script is to do it in 2 minutes without errors and confirmations via SMS.

Mistakes.

The mistake is to design only for the happy path. It’s important to work through negative-twig scenarios: what if the confirmation code didn’t come in, what to do if there was no contact or the app was hanging.

How to Build a Customer Journey in a UX Project

Stages of creation

1. Research – understand users, their tasks, contexts.
2. The path map is to visualize each stage: from trigger to outcome.
3. Pain Points – Verify bottlenecks and anticipate improvements.
4. Test solutions – quickly test hypotheses (polls, usability tests).

Example

When you launch a B2C product, the team first analyzes reviews, searches, interprets heatmap on the site. Uses CJM for visualization, finds three points of loss of users — complex registration, long email confirmation, unclear order statuses. Simplifies registration, improves communication, adds progress bar.

Tools and sources

To create CJM, Miro, Figma, Smaply, CustDev interviews, analytics metrics (Google Analytics, Yandex.Metrica) are most often used. Qualitative and quantitative indicators are analyzed. For benchmarks and interviews, you should go to NNGroup and watch UXMatters.

How to Use Scripts to Improve UX

Highlight key scenarios

Rate scenarios by frequency, business value, and user complexity, starting with the most frustrating or mass-produced scenarios.

Work through the bad scenarios.

For each scenario, look for errors, exit points, crash points, see if you can cut down on clicks, cut down on extra steps, make things more visual.

Example

In SaaS, the application service, users lost data when they misplaced the submission, the script was superficial, didn’t take into account deviations, and the solution was to add autosave and validation at the input stage, not just at the final submission.

Mistakes and anti-patterns with customer journey and scenarios

Don’t ask users

If you build only on internal discussions, the user path will not be a real one, but an abstract one.

Ignore the edge cases

Bad UX always comes up with exceptions: payment failure, customized task, missing one of the steps of the path, and then you lose loyalty.

No connection to metrics.

If CJM lives apart from analytics, there’s no result. Each node, step or step has to be linked to the metrics: CR (conversion rate), NPS, CSAT, the number of errors in the script. Metrics are, for example, in Appcues.

FAQ

Why do you need a user path map?

To understand the real problems and expectations of users, rationally improve the product, save resources on improvements.

What is the difference between user flow and customer journey map?

User flow is a diagram of user movement across an interface, often for a single task. CJM is a look at all points of contact, including non-product and emotional aspects.

What tools are used for CJM?

Miro, Figma, Smaply, CustDev interview, analytics.

How to check if the map is correctly constructed?

Get feedback from users, analyze metrics at each stage, and conduct custdev research regularly.

What are the differences between use cases and scenarios?

The scenario includes context, goals, alternative branches, and cases are often just short descriptions of tasks.

What is the main indicator of success with CJM?

Increased user satisfaction (CSAT, NPS), reduced error rates, and increased re-requests.