Customer journey mapping from interviews: how to build a CJM

A customer journey map shows what the customer experiences

A customer journey map, or CJM, shows the steps a person takes to reach a goal. It records stages, touchpoints, questions, difficulties, and opportunities for improvement. Interview data helps explain why they acted. The map should keep evidence and assumptions distinct.

Start with one scenario. “All customers over time” is too broad. “A person books their first trial class and attends it” is a usable scope. The sale of a membership after the class can be mapped separately.

How to build a map from interview recordings

1. Specify the person and their goal

   Describe the person through their situation. For example, a beginner is looking for an evening class near work. Keep that journey separate from a regular customer renewing a membership.

2. Reconstruct the actual order

   List events as they happened: what came first, what followed, and where the person backtracked. Preserve the order even when it makes the diagram less tidy.

3. Attach the evidence

   Save the interview number and timecode for each important finding. If the person said they were confused, that is evidence. If the team inferred the feeling, mark it as a hypothesis.

4. Group similar steps into stages

   Name each stage for what the person does. “Choosing a suitable time” says more than the internal term “lead qualification.” Keep exceptions that change how the journey should be understood.

5. Mark barriers and gaps

   Distinguish missing information, inconvenience, and an action the person cannot complete. If nobody described a stage, mark it “no data” instead of assigning a presumed emotion.

6. Choose one improvement to test

   State which barrier you want to reduce, what you will change, and what observation will tell you whether it helped. Making a map alone does not change the customer’s experience.

Booking a class for the first time

This fictional example is unrelated to research at a real school. The interviewee found the schedule quickly but could not tell whether the class suited beginners. They booked after calling and then had trouble finding the right entrance. “The website is hard to use” is too broad to account for the issues described.

Avoid charting a mood drop as “minus five” if the person never rated the experience that way. “Didn’t understand,” “asked,” and “looked for it,” with a reference to the original remark, are enough. Use separate evidence rows for different interviews. A pattern in two accounts is a reason to investigate the barrier, not a percentage of all customers.

Before changing the page, check other sources such as a support request, direct observation of someone doing the task, or available analytics events. Conflicting evidence can show that people followed different routes.

Keep observations, explanations, and solutions distinct

The team may assume the customer called because the site was confusing. The recording might reveal a different reason: “I understood everything. I just wanted to meet the instructor.” The action is the same. Revisit the surrounding context before drawing a conclusion from a quote.

Label the current and desired journeys separately. Removing the call from the future map does not remove it in practice. Assign each proposed change someone to run the test and a date to review the result. Save the map version and its interview list so you can add new evidence without losing the history.

A CJM template for one scenario

Person and situation:
Customer’s goal:
Journey start and end:
Interviews used:

Stage:
Person’s action:
Touchpoint:
Their question or expectation:
Observed difficulty:
Quote / interview / timecode:
Emotion: reported or inferred?
Data gap:
Improvement idea:
How will it be tested and by whom?

• One scenario and a clear point of view.
• Important findings have evidence.
• Unknowns are recorded as unknowns.
• A proposed improvement is still a hypothesis until tested.