Customer Journey Research: Methods, Maps & Examples

Customer journey research follows an attempt to buy or use something across the encounters that shape it. Connect recorded actions with the customer’s account, available alternatives and service conditions. The aim is to identify the obstacle, choose who can fix it and observe whether the change helps the customer complete the task.

A reminder, shorter checkout and clearer offer may solve different problems. Find out why the attempt stopped before choosing among them.

Example: a membership without an available class

Lantern is a hypothetical fitness studio selling regular after-work classes. Maya wants a Monday evening class with a friend. She discovers an ad, enjoys a trial and starts membership checkout. The dashboard records an unfinished enrollment.

“Reduce checkout abandonment” describes the business's symptom. Maya's task is more specific: establish a routine she can actually attend. A membership is useful only if a suitable class is available at the required time.

That distinction sets the research boundary. Begin before checkout, when Maya forms an expectation about the schedule. Continue until she joins, chooses another option or stops looking. Include the studio visit, staff conversation, booking system and friend who affects the choice.

This follows the principle behind mapping a user's whole problem: investigate how online encounters, offline encounters and the processes behind them join up. A map organized only around departments can miss the handoff that matters to the customer.

Our customer needs analysis guide helps distinguish the desired outcome from a requested feature. Here, “show me a better calendar” may be a proposed solution. A dependable Monday routine is the need it must serve.

One connected account of what happened

Reconstruct Maya's attempt before summarizing it as a theme such as convenience or trust.

Keep each source and its limits with the entry. Attendance records confirm a visit. A later interview records Maya’s memory of a conversation, not the instructor’s original words.

Link records only when the evidence supports it. Maya’s permission to review her confirmations and messages can help. Similar timing does not connect an unrelated phone session and laptop visit to one person. Leave unmatched encounters unlinked.

Check transaction records as well as analytics. A missing purchase event does not prove no purchase occurred. A checkout visit does not prove someone bought.

An event and its explanation are different evidence

Maya says: “I liked the class. I couldn't tell whether paying would get me a place after work.” In the interview, she describes choosing another studio with a bookable weekly place that fits her schedule. Lantern has her account of that choice, rather than the other studio's transaction record.

That account gives the team a plausible explanation: Lantern communicated permission to book when Maya needed confidence that a usable place existed. It does not establish that every unfinished enrollment has the same cause.

Three possibilities lead to different work:

• Misunderstanding: a suitable place exists, but the customer cannot discover or interpret it. Clearer availability information may help.
• An unmet condition: the required class is full. Better wording cannot create a place. The schedule or membership offer needs attention.
• An experience failure: a suitable place is available and understood, but enrollment or booking fails. Reproducing the failure matters more than another message test.

Check the booking history and eligibility rules for the dates in the episode. “Monday is full today” cannot establish what Maya could book last week. Ask the support team to interpret its reply, and check whether the same answer appears on the website and at the studio.

Keep other explanations alive. The membership commitment, the friend's availability or a payment problem may also matter. Maya's account helps choose what to investigate; it does not isolate a causal effect by itself.

Lantern then checks the dated booking history. The Monday class had no available places when Maya inquired, and membership did not reserve one. That establishes an unmet condition in this episode. The support reply explained access without resolving it. A shorter checkout could not supply the place Maya needed.

Find the case that challenges your preferred story

Sam sees the same waitlisted Monday class and joins anyway. He works flexible hours and can attend on Tuesday morning. He understands that membership gives booking access rather than a reserved weekly place.

The waitlist has not disappeared. Its significance changes with the customer's alternatives.

The contrast narrows the research question. Study people who need one fixed session apart from those with several workable choices. Calling both “busy professionals” hides the condition that changes the offer.

It also changes the proposed fix. A general reassurance that there are plenty of classes could disappoint Maya while accurately describing Sam's options. Useful information shows the times that are available to that customer and the commitment the offer actually supports.

Seek other contrasts deliberately: someone who bought despite uncertainty, someone who understood the rules and left, and someone who could not complete an otherwise suitable purchase. Choose these accounts to test explanations, not to estimate their prevalence from a small selected sample.

Choose the method for the question still open

More interviews with happy trial attendees may produce praise without explaining why enrollment stopped. Choose the next study around the missing answer.

Start with recent attempts from people who joined, delayed and chose an alternative. Ask them to reconstruct the sequence using the material they actually encountered. “What happened after you looked at the schedule?” is more useful here than “Would clearer information make you join?”

Our qualitative market research guide explains how to preserve the episode and examine competing interpretations. Where a task needs checking, watch someone try it with their usual device and relevant circumstances. Contextual observation can reveal barriers and workarounds in the setting where the activity happens. An explanation given during that session still needs to be distinguished from the action observed.

Then check operational feasibility. For Lantern, that means booking rules, available places, waiting-list behavior and what staff can promise. If everyone who needs Monday evening faces a full class, a new enrollment message addresses the wrong problem.

To investigate what the service team tells a new enquirer now, use our mystery shopping research guide to plan a realistic unannounced encounter. The check can locate a handoff to fix; it cannot recreate Maya's earlier conversation or explain her decision.

Use a broader measurement study when you need to know how common each constraint is. Define the population and recruit beyond easy-to-reach customers. A waitlist theme among selected interviewees does not estimate the share of all prospects blocked by capacity.

Assign the change to the team that can make it

The journey investigation should leave Lantern with a decision about what to change first.

Show availability before payment and stop implying that membership guarantees Maya’s Monday routine. Operations must decide whether a dependable place is possible. The digital team must make the actual options clear. Both are needed.

If no place exists, Lantern must decide whether it can provide one or should direct that customer elsewhere. A successful journey can include helping someone recognize a poor fit before buying. Counting every additional enrollment as improvement would reward a promise the studio cannot deliver.

Retest the behavior the change is meant to enable

Suppose Lantern introduces an availability view before membership enrollment. The hypothesis is that people with a usable session can identify it and proceed with a clearer understanding of what they are buying.

First test comprehension and the task itself. Can the person identify an available class, explain whether the place is reserved and complete the relevant booking? Correct answers in the session show that those participants understood the view. They do not show that it will sell more memberships.

For a live evaluation, follow eligible customers through purchase, a suitable booking and attendance. Set the period to fit the normal decision cycle before reading results. Keep people without a suitable class visible; do not remove them afterward to improve conversion.

Check consequences beyond the next click: refunds, early cancellations, booking-related support and whether existing members lose access to suitable sessions. Microsoft's experimentation guidance emphasizes a specific hypothesis, success and guardrail measures, and an appropriate unit of comparison.

Capacity complicates this example. A place booked by one customer is no longer available to another. Ask the analyst to design a comparison that accounts for shared class capacity; two groups competing for the same small pool of seats may affect each other's outcomes. A simple before-and-after improvement, especially after a schedule change, does not isolate the effect of the new view.

For people who cannot obtain a suitable session, clearer information may reduce enrollment while preventing a poor purchase. For people who can, the next evidence is whether they book and attend. Evaluate those outcomes separately before deciding whether to keep the change or investigate another cause.

Example: signup without first feedback

A completed signup can start another journey rather than finish the customer's task. Consider Reviewroom, a hypothetical file-review service for independent designers and their clients. A designer creates an account and uploads a proposal, but the client never leaves feedback. The product team must decide whether to clarify the invitation step, repair a failure or reconsider what the designer needed from this first session.

Define first value as a client leaving useful feedback on the intended file. Signup, upload and invitation clicks are earlier steps. Set the period around the normal review cycle before checking results. Keep every eligible signup in view, including people who never upload.

Use dated records for signup, saved file, requested invitation, delivery, access and saved feedback. An invitation request does not prove delivery. Missing feedback may mean no reply, failed tracking or a reply elsewhere. Check underlying records before calling it abandonment. Keep uncertain matches unlinked.

The designer's expectation determines the next investigation. They may believe uploading automatically invites the client, stop because the file did not save, or deliberately wait for a revised proposal before inviting anyone. Those explanations imply different changes. Interview recent signups about the actual review they tried to arrange, then watch relevant designers attempt the upload-and-invite task. Ask what will happen next before explaining the interface. Observe whether the intended client can open the file and respond under the real access rules.

A wording change might make the invitation step explicit. A repaired upload needs a successful saved file. A client-access problem needs the correct permission or access path. If the designer was not ready to request feedback, repeated reminders could rush the wrong task. Include a designer who reached feedback and one who completed the process through another channel to challenge the preferred explanation.

A simulated walkthrough can suggest where instructions invite the wrong expectation. Its apparent friction is a hypothesis, not an observed usability failure or proof that a real client received an invitation. Test proposed wording or feasible alternatives, then use actual task observation and events to decide whether the path works.

In a live evaluation, keep the original signup count and follow each step through the agreed period. Compare useful first feedback with access failures, support requests and unwanted invitations. More invitations without more completed reviews leave the problem open. The goal is feedback a designer can use.

Offer comparisons can inform the next studio test

At Sapien, we build simulated audiences from purchase, behavioral and research data. Customer data and prior research can add context. We compare reactions to complete offers or messages and explore why buyer groups respond differently.

If operations can support a defined weekly-place offer, Sapien can compare simulated responses to it and the existing open-booking membership using complete terms. Those reactions help choose what to investigate; they do not establish who visited, booked or attended. Our synthetic versus human respondents guide explains the handoff to firsthand accounts and behavioral evidence.

Scope the membership comparison with Sapien using both complete offers, the available class capacity and eligible customer situations. Keep the later purchase, booking and attendance measures in the plan.