A customer ordering a plant-care kit may leave the checkout page to find out whether the kit suits a shady apartment. Your sales report might show only an abandoned cart. A journey map gives you a place to record that detour, mark what you don’t yet know, and decide what to ask a customer.
A practical example
A customer ordering a plant-care kit may leave the checkout page to find out whether the kit suits a shady apartment. Your sales report might show only an abandoned cart. A journey map gives you a place to record that detour, mark what you don’t yet know, and decide what to ask a customer.
A map from the buyer’s side of the counter
These are illustrative entries, not findings about real customers. A useful map leaves room for “we don’t know.”
| Moment | Evidence you might have | Question still open |
|---|---|---|
| Discovery | A buyer says a friend sent the product page. | What did the friend say it would help with? |
| Choosing | A visitor asks whether the kit suits a north-facing window. | Could they find the light requirements before checkout? |
| First use | A support email asks which packet to open first. | Are the packet labels consistent with the instructions? |
| Reordering | An existing customer asks for a refill rather than another kit. | Is a refill available, and can they find it? |
Don’t join four observations from different people into one supposedly typical buyer. Date each observation and keep the source with your working notes. Where you have only a theory, keep it in the question column.
Choose one improvement to test
After mapping the journey, pick the friction point that is important to customers and that you can reasonably change. Make the improvement specific: add a clear size guide to the product description, explain what happens after an order, or give staff a short response for a repeated question. Avoid redesigning every stage at once, because you will not know which change helped.
Decide what observation would indicate improvement. You might listen for fewer repeated questions about one detail, ask customers whether they found the instructions they needed, or compare the same step before and after a change. Use measures that fit the issue; do not treat a small change in a small sample as proof of a universal trend.
Keep the map alive
Customer behavior can change when products, channels, staff, or policies change. Date the map, note who contributed, and review it when you see a recurring problem or make a substantial change. Keep the working version simple enough that someone can update it after a conversation or support review.
A useful map is a tool for choosing the next improvement, not a promise that every customer follows one route. Start with one audience and one goal, make the uncertainties visible, and revisit the journey after you test a change.
Set a useful starting point
Choose one customer group and one goal for the map. A map for someone ordering a plant-care kit for the first time will differ from a map for a returning customer who needs a refill. Keep the scope narrow enough that you can describe real interactions rather than every possible path through the business.
Define where the map begins and ends. It might start when a person first notices a need and end after they have used the product and decided what to do next. Include the steps that happen before and after the sale; the checkout alone is not the whole journey.
Write the stages in the customer’s order
List the main stages in plain language. For a first-time online order, they could be: notice a problem, look for options, compare offers, place an order, receive and use it, and decide whether to contact support or buy again. The exact stages depend on the customer and the type of offer. Do not add a stage just because a marketing diagram usually includes it.
Under each stage, note what the customer does, where the interaction happens, what question they may have, and what could make the next step harder. For example, a reader comparing kits may want to know what is included and whether the instructions fit a beginner. If that information is missing, they may leave to search elsewhere or ask support. Record the observed behavior and the possible explanation separately.
A simple table is enough: stage, customer action, question, evidence, friction, and the person responsible for the next handoff. Make a separate map when a different customer group follows a meaningfully different path. Do not create dozens of hypothetical branches; include an alternate route only when you have evidence that it changes what the customer needs or what your team must do.
Use evidence instead of assumptions
Review actual customer questions, support conversations, order steps, feedback, and staff observations. Ask people to walk through a recent experience in their own words. Use notes that describe what happened: “The customer emailed to ask which pot size fits the kit” is more useful than “Customers are confused.” Protect private details when sharing examples and do not include personal information that the map does not need.
For each stage, label what is known, what is inferred, and what still needs checking. One complaint may reveal a problem worth investigating, but it does not automatically show that every customer has it. If you have analytics, use them to locate a point where people stop, then gather context to understand why. A drop-off alone does not explain the reason.







