User journey
Definition
A user journey is the full sequence of steps, actions, and touchpoints a user goes through when interacting with a product to accomplish a goal. In SaaS, a typical journey includes pre-product touchpoints (marketing, signup), the activation arc (first session, aha moment, completed onboarding), ongoing usage (regular workflows, feature adoption), and key lifecycle events (renewal, expansion, support). User journeys can be short (a single task) or long (a multi-month adoption arc). User journey mapping is the practice of visualizing the journey explicitly — listing each step, the user's intent, the emotional state, the touchpoint, and the moments where the experience breaks. It's a research and design tool used to align product, design, marketing, and CS teams around the same picture of how users actually move through the product.
Why it matters
Most product teams optimize touchpoint by touchpoint: improve onboarding here, fix that feature there. A user journey view forces a systemic question instead — how does each touchpoint connect to the next, and where does the chain break? It's how teams find the upstream fix that solves five downstream problems, and how they avoid local optimizations that look like wins but don't move retention.
How it works
User journey work typically combines: (1) mapping — researching and visualizing the actual steps users take, often using interviews and analytics; (2) instrumenting — tracking the events that mark each major step so the journey is measurable, not just qualitative; (3) identifying drop-offs — finding the steps where users stall, churn, or take unintended paths; (4) intervening — using onboarding guides, in-app guidance, and product changes to repair the broken steps; (5) re-measuring — confirming the journey actually improved, not just one isolated metric.
Related terms
Related resources
Frequently asked questions
What's the difference between a user journey and a customer journey?
User journeys focus on what an individual user does inside the product. Customer journeys are broader — they include pre-product steps (marketing, sales, procurement) and the full account-level relationship (multiple users, expansion, renewal, advocacy). Most product teams work with user journeys; marketing and CS teams typically own the broader customer journey view.
How do you map a user journey?
Start with a specific user goal and a specific persona. List the steps the user takes to reach the goal, the touchpoints involved, the user's likely emotional state, and the moments where the experience breaks. Combine qualitative inputs (interviews, support transcripts, session replays) with quantitative ones (funnel analytics, event tracking). The output is a shared artifact the team can act on, not a one-time deliverable.
Where do in-app guides fit into a user journey?
Guides are the intervention layer. Once a user journey reveals where users stall — say, between sign-up and first valuable output — a multi-step guide is one of the highest-leverage tools for closing that gap. The journey tells you where to intervene; the guide is one of the ways you intervene.