Back to blog

Customer Journey Mapping: Basics and a B2B Example

Shusaku Yosa

カスタマージャーニーとは?マップの作り方から活用事例まで徹底解説

A customer journey describes the experience of recognizing a problem, exploring alternatives, buying, using and potentially continuing with a solution. A journey map organizes actions, questions, touchpoints and obstacles. A campaign calendar alone does not describe that experience.

Journey maps, personas and funnels

Concept

What it explains

Example question

Persona

Who faces the problem and under what conditions

What responsibilities and constraints affect the buyer?

Journey

How experience and questions change

What information is missing during evaluation?

Funnel

Volumes and rates between defined stages

How many inquiries become qualified opportunities?

These views complement each other. Describe buying-relevant circumstances rather than inventing detailed personal traits. Funnel data can reveal where to investigate, but interviews and support records may be needed to understand the reason behind a drop-off.

Set the boundaries first

Specify the product, audience, question and start and end points. A map from inquiry to contract needs different evidence from a map of onboarding and retention. Combining new and existing customers too early can hide important differences.

In B2B, users, budget holders and procurement teams may participate at different times. Include important handoffs and approvals rather than assuming one person moves through the entire process. People can return to comparison or use multiple touchpoints at once; a straight-line map is an organizing device, not a claim that every journey is linear.

A fictional B2B service journey

Stage

Customer action or question

Touchpoint / possible obstacle

Recognize problem

Reduce manual work, but identify the real cause

Search and colleagues / unclear diagnosis

Research

Understand approaches and preparation

Articles and resources / unfamiliar terminology

Compare

Assess costs and operating differences

Pricing and demos / hidden implementation effort

Decide internally

Explain the purchase to other stakeholders

Proposal and comparison / unanswered concerns

Adopt and continue

Set up and use the service

Guidance and support / unclear ownership

This table is an illustrative hypothesis, not research findings. Replace it with evidence from your customers. If you include emotion, use the person’s words or supporting behavior and identify inferences explicitly. Do not treat a guessed feeling as an observed fact.

Separate evidence, interpretation and action

Record type

Example

How to use it

Observed evidence

An interviewee asked about additional fees

Record audience, timing and wording

Hypothesis

Unclear cost boundaries delay decisions

Do not assume it applies to every buyer

Further research

Review inquiries and additional interviews

Look for differences by segment

Proposed change

Explain included and extra costs in a table

Assign an owner and evaluation method

Build the first map

  • Write the customer’s actions before placing company touchpoints beside them.
  • Collect interviews, sales and support records, and usage evidence; retain the source.
  • Leave unknown stages marked as unknown and prioritize the missing research.
  • Review the map with sales, delivery and support to detect conflicting customer situations.
  • Choose one important obstacle and define a change and a way to evaluate it.

Use and maintain the map

A map is useful when it changes work. If you improve setup instructions, observe setup completion. If you clarify comparison information, examine the quality of subsequent inquiries. Check the relationship with revenue and retention over an appropriate period, without promising that drawing a map will automatically increase conversion.

Keep the audience, research date, owner and unresolved assumptions visible. Update the map when the product or buying process changes. For a facilitated workshop and a method to connect obstacles to projects and budgets, use the related implementation guide.

Back to blog