What is a customer journey map?
A customer journey map represents the steps someone takes while trying to achieve a goal with a company or product. It brings the person, scenario, stages, and experience into one view. Nielsen Norman Group describes journey mapping as a way to understand that experience over time, including actions and the thoughts and emotions supported by research.
For a SaaS, the journey may begin before signup and continue beyond onboarding: discovering a problem, evaluating options, getting a first result, returning for another job, and deciding whether to renew. A screen-by-screen product tour covers only part of that path.
Choose a defined question before mapping everything. ‘Where does a freelance designer’s first client brief become difficult?’ gives the exercise a decision to support. ‘Document the entire customer experience’ can create a large diagram without clarifying what should change.
Choose one actor, scenario, and map type
Start with one person in one situation. A freelancer buying a tool, the client answering a brief, and a studio administrator approving access have different tasks. You can connect their maps later, but combining all roles in the first row can hide who actually encounters the problem.
State whether the map describes the current experience or a proposed future experience. A current-state map needs observations of what happens today. A future-state map describes a design to evaluate. An assumption map can help plan research, provided every unverified claim remains labeled as an assumption.
Our worked example is an original assumption map for the fictional BriefBoard client-brief app. It contains constructed situations to illustrate the method. It is not based on customer interviews, a usability study, or a measured ShowMeYourSaaS customer journey.
Actor: a freelance designer preparing the first brief for a new client. Goal: receive enough project information to begin a useful scope discussion. Scenario: the client has agreed to discuss a project but has not supplied the brief. Scope: discovering a tool through the first repeat use and renewal decision. Map type: assumption map for research planning. Evidence status: all example experiences below are hypotheses to investigate.
A worked SaaS customer journey map
Organize the experience around the customer’s job rather than your internal departments. A person may move between search, a pricing page, an email, a client-facing form, and a support conversation. The map should still follow one goal across those touchpoints.
The table below turns each fictional stage into an evidence question. It deliberately avoids assigning invented emotions such as ‘delighted’ or ‘frustrated.’ If a participant later describes a feeling, record the actual context and an appropriate source reference.
| Stage | Customer’s task | Touchpoint | Question to investigate | Possible owner |
|---|---|---|---|---|
| Discovery | Find a better way to request a client brief | Search result or relevant recommendation | Does the description match the job the designer means? | Founder / content |
| Evaluation | Check whether the tool fits this project | Demo, examples, pricing | Are limits and the client’s required effort clear? | Founder / product |
| First value | Receive a usable first response | Brief setup and client form | Where do sender or recipient need help? | Product / support |
| Repeat use | Start the next project with less rework | Saved briefs and a new request | Which information should be reused or changed? | Product |
| Renewal | Decide whether continued access is useful | Usage history and billing information | Is recurring value visible at the customer’s natural cadence? | Founder / customer success |
Collect evidence at the point where the task changes
Use recent task interviews, observed sessions, permitted support records, and appropriately collected product events. An event can show that a step was attempted; it may not reveal why the person stopped. A customer explanation can suggest a cause; it may need observation before you change the interface.
Keep observation, interpretation, and proposed improvement separate. A constructed example is ‘The participant copied a request into a personal email.’ One possible interpretation is that the invitation was unclear. Another is that the client requires a familiar channel. Ask what happened before deciding the only answer is a redesigned invitation.
Attach a source reference, date, role, and evidence status to each important note. Summaries used for broad planning should avoid exposing private customer material. Keep access to the underlying research appropriate to the people doing the work. The customer interview guide helps collect task context.
Turn a journey problem into an owned improvement
Choose a problem supported by evidence, then state the expected behavior after the change. In the fictional brief workflow, a possible investigation could ask whether recipients understand what to provide before opening the form. A proposed improvement would be a clearer invitation and a short explanation of the requested information.
Assign an owner, a bounded next step, and a review window tied to the job’s cadence. Check both sides of the handoff: a sender can successfully create a link while the recipient remains unable to answer. An improvement is useful when the whole task becomes easier to complete, not merely when one button gets more clicks.
Use a small decision record: evidence, problem, change, acceptance check, outcome, and remaining uncertainty. If you do not yet have evidence, the next action may be an observation session instead of a feature. Link larger product decisions to a product roadmap so ownership remains visible.
How does a journey map differ from a funnel or an onboarding checklist?
A funnel summarizes movement through defined conversion stages. A journey map adds the person’s task and experience across touchpoints, including movement that is not linear. Someone may return to pricing after a support conversation or ask a colleague before completing a trial.
An onboarding checklist describes steps needed to get started. The journey map can reveal why those steps are confusing, who else participates, and what happens before and after them. Use the activation guide for the first useful result and the onboarding email guide for messages supporting that result.
A detailed operating blueprint may also describe internal systems and handoffs behind the experience. Keep those details in the artifact needed by the implementation team. The first customer map should remain readable enough to explain where the customer’s goal is helped or blocked.
Keep the map current and download the editable template
Version the map when the actor, product flow, or evidence changes. Record what was learned and whether it confirmed or contradicted the earlier assumption. A polished map that still describes an obsolete signup flow is a weak basis for choosing the next improvement.
The download contains the fictional completed example plus a blank structure for your own actor, stages, evidence, owners, and review decisions. It is our original worksheet, not a reproduction of another provider’s canvas. Method source checked October 26, 2026.