Journey mapping
Also called customer journey mapping or user journey mapping.
Journey mapping is a way to visualize the steps a person takes to achieve a goal with a business, including their actions, touchpoints, thoughts and emotions. Businesses use it to find friction and improve the customer experience.
How it works
Choose one customer type and one goal, such as returning a purchase or getting a first useful result from software.
Map the experience from the customer's perspective, not your departments' internal workflow. For each stage, record what the customer does, where they interact with the business, and what helps or frustrates them. Use interviews, support requests and behavioral data. Label guesses as hypotheses.
Finish with specific improvements and someone responsible for each one.
Finding friction between signup and a first result
A fictional software startup follows one cohort of 100 trial users through to purchase. Counts are illustrative; the possible friction points need research.
| Stage | Users reaching it | Customer goal | Possible friction |
|---|---|---|---|
| Trial signup | 100 | Know where to start | Generic welcome screen |
| Data import | 60 | Use their own data | Confusing file requirements |
| First report | 30 | Get a useful answer | Unexplained filters |
| Paid subscription | 10 | Keep using the product | Unclear pricing |
Only 30 ÷ 100 = 30% reach a first report. The map gives the founder a concrete onboarding problem to investigate before spending more on acquisition. It does not prove that file requirements caused the drop-off.
A useful next step is to observe users attempting the import, fix the confirmed obstacle, then measure completion again.
Questions people ask
Is journey mapping the same as a sales funnel?
No. A funnel measures how many people progress between stages. A journey map explains the experience around those steps, including interactions outside your website and what happens after purchase.
Do you need special software?
No. A spreadsheet, whiteboard or shared document works. Evidence matters more than presentation: a polished map built entirely from the team's assumptions is still a hypothesis.
