Prefer English?
Prefer English? Switch the website language for a better experience.
A user journey is the path a person follows to reach a goal with a product, service or website, including what they do, think and feel along the way. It is usually drawn as a map, so a team can see where the experience works, where it grinds, and what to fix first.
The two terms are often swapped, and the difference is mostly one of scope. A user journey follows a person toward a goal inside a product or site: sign up, book a demo, finish checkout. A customer journey covers the whole relationship with a company, from the first ad seen to renewal or support, across channels and often across months. A user journey usually sits inside a customer journey, as one chapter of a longer story.
Practitioners draw maps in many styles, yet the building blocks repeat. Nielsen Norman Group lists five (article consulted in October 2026):
A map drawn in a workshop with no data is a plausible story, not a measurement. Mix the sources: interviews, session observation, surveys, session recordings, analytics (exit pages, form abandonment), and the questions that reach support and sales. Interviews tell you why, numbers tell you where. Using both avoids fixing a problem that nobody has.
Picture a marketing team that wants to understand how visitors end up requesting a demo. The map shows four phases: discover (an article found on Google), evaluate (the product page and the pricing page), hesitate (looking for reviews and case studies) and request (the form). In the “hesitate” phase, the person wants proof and cannot find it within one click. That is a clear opportunity, tied to a measurement: how many visitors leave between the product page and the form. The scenario is illustrative. It shows the method, not a result.
Teams generally draw two kinds of maps. A current-state map describes what users go through today, and works as a diagnosis. A future-state map describes the experience the team wants to deliver after changes, and works as a roadmap. Starting with the future state is daydreaming. Starting with the current state tells you why anything needs to change. When the team also needs to see what happens behind the scenes (the people, tools and processes that make each step work), a service blueprint extends the map on the organization side.
A well-drawn journey helps SEO too. It reveals the questions someone asks at each phase, and therefore which content to write and which queries to target. A visitor hesitating before a demo request looks for reviews, comparisons and case studies, which are pages to produce and link together. On the conversion side, the map shows where a call to action belongs and, just as usefully, where it would be premature. Nobody wants to be asked for a meeting before understanding what the product does.
On a website, the journey guides the site structure, the content needed at each stage and the placement of calls to action. It feeds UX design, it gives a reading grid to analytics, and it sets the scene for the wireframes and the prototype tests that follow. In our UX/UI and Product design missions it belongs to the user research and audit that come before a redesign: see our UX/UI and Product design expertise.
Code
Over 180 companies have already stepped out of the shadows with us.
The user journey is the set of steps a person goes through to reach a goal on a digital product, from discovery to conversion. Mapping it out shows friction points, key moments and where to improve, so decisions rest on real behavior rather than assumptions.
A user journey covers the whole path to a goal, from discovery to conversion. A user flow is narrower: the sequence of screens and actions a person follows inside the product to complete one task. The journey tells the story, the flow maps the clicks.
