How to Create a Customer Journey Map — A Practical Guide to Customer Experience Design

"We made a customer journey map. But in the end, nobody looks at it." This situation occurs frequently on project sites involving service design and website renewals. A map carefully created by the contractor's web director sits untouched in the client's drawer after delivery. Or a map produced by an internal marketing team over several weeks is replaced by other materials without ever being referenced during campaign planning.

Why does this happen? There are two root causes.

The first is that "creating the map" becomes the goal itself. Staff assigned to create a customer journey map focus on producing something that looks good. Rather than actual customer data or interview results, the team's vague assumptions about "what the customer is probably like" accumulate, resulting in a map that lacks realism.

The second is that there is no utilization flow designed after completion. Even if a polished map is handed over, the recipients often have no idea how to incorporate it into their workflow. Without clarity on how to reference the map when making decisions, or when to update it, the map naturally falls out of use.

The inherent value of a customer journey map lies in visualizing the entire experience from the customer's perspective — aligning the perception of different departments within an organization, and bridging the understanding between clients and contractors around shared issues. Extracting this value requires designing not just how to create the map, but how to use and maintain it.

A customer journey map is a diagram that describes, along a chronological series of phases, the actions, thoughts, emotions, touchpoints, and issues that a specific persona encounters while working toward a goal (such as purchasing a product, using a service, or submitting an inquiry).

Persona

The hypothetical customer profile that anchors the map. It includes age, occupation, living environment, behavioral characteristics, and values. When multiple personas exist, a separate map is created for each. Trying to pack multiple customer profiles into a single map tends to produce abstract descriptions that don't reflect any specific person's actual experience.

Phases (Stages)

The stages through which the customer progresses toward their goal. Divisions such as awareness, consideration, purchase, use, retention (or repeat), and advocacy are common, but the appropriate phase structure varies by service and industry. A practical rule of thumb for phase granularity: divide phases at the level where the relevant tactics change from one phase to the next.

Touchpoints

Every point of contact between the customer and the brand, service, or representative. This includes search engines, social media, advertising, landing pages, emails, phone calls, in-store interactions, contracts, and invoices. Touchpoints should be identified comprehensively without distinguishing between online and offline. From the contractor's perspective, distinguishing between touchpoints they can directly influence and those managed internally by the client clarifies the boundaries of responsibility in later tactic planning.

Actions, Thoughts, and Emotions

For each phase, describe what the customer is doing (actions), what they are thinking (thoughts), and how they feel (emotions). Emotions are typically visualized as a curve from positive to negative. The point where emotions drop most sharply is the "moment of pain," which becomes the primary target for improvement initiatives.

Issues and Opportunities

Record the barriers and friction the customer faces at each phase as "issues," and describe the potential for improved experience if those barriers are removed as "opportunities." These two axes are the critical output that connects the customer journey map to tactic planning.

Step 1: Define the Persona and Set the Scope

The first decisions to make are: whose journey is being mapped, and through which phases. Use real data for persona definition. Extract patterns from actual customer purchasing and usage behavior using interviews with existing customers (at least 5 people), surveys, CRM data, inquiry logs, and support records. When data is insufficient, create the map with hypotheses clearly labeled and simultaneously develop a data collection plan to validate those persona assumptions.

Set the scope concretely — for example, "from awareness through one month after purchase." Trying to pack an entire customer lifetime into a single map reduces granularity to the point of losing practical utility. Starting with the phases where issues are most concentrated and expanding from there tends to produce more actionable results in practice.

When clients and contractors create the map together, clarify during the scope-setting stage "which side leads which phase." For example, making explicit that awareness through lead acquisition is the client's domain while post-lead-acquisition web conversion tactics are the contractor's primary responsibility prevents confusion in later tactic planning.

Step 2: Exhaustively Identify Touchpoints

List every contact point the persona passes through on the way to achieving their goal. In a brainstorming format, have all team members write contact points on sticky notes (or an online whiteboard) and organize them by phase.

A common pitfall during identification is listing only the touchpoints that the team is directly involved in. Customers gather information and make decisions through channels that service providers never intended. For example, checking reputation on review sites before visiting the company website, or referencing a friend's social media post, are behaviors that both clients and contractors often overlook. Making these "unmanaged touchpoints" visible is one of the core purposes of the customer journey mapping process.

After identifying touchpoints, evaluate each one: "What does the customer expect here?" and "Does the current experience meet that expectation?" Touchpoints where the gap between expectation and reality is largest become the priority targets for improvement.

Step 3: Draw the Emotion Curve and Extract Issues

Visualize the emotional ups and downs across each phase as a curve. Plot on a grid with positive-to-negative on the vertical axis and phases on the horizontal axis — mapping where the persona experiences joy, anxiety, disappointment, and relief.

Drawing the emotion curve requires data from customer interviews. Reflect verbal data gathered from questions such as "How did you feel when you decided to purchase?" and "Was there a moment during the process when you felt uncertain?" in the emotion curve. For phases where emotions drop sharply (moments of pain), dig deeper into "why that emotion arises" and record the underlying issue as a concrete statement.

Write issue descriptions from the customer's perspective: "cannot make a judgment because X is unclear," or "exhausted by the number of steps in X." Not "information is lacking" but "since spec and price comparison information cannot be found in one place, users end up navigating between multiple sites." Abstract issue descriptions cannot be directly translated into tactics, causing interpretation gaps at the implementation stage.

Step 4: Prioritize Issues and Organize Tactic Hypotheses

Evaluate the identified issues on two axes — impact (magnitude of effect on customer experience) × feasibility (constraints of technology, budget, and time) — and determine priorities.

The basic approach is to address issues that are high in both impact and feasibility first. However, clients and contractors often weight these axes differently. Contractors tend to prioritize feasibility from a system implementation standpoint, while clients often prioritize impact because a given issue directly affects revenue if left unresolved. Conducting this priority evaluation jointly during the map creation stage significantly reduces alignment costs later in tactic planning.

Write a one-sentence "tactic hypothesis" for each issue: "Adding a product comparison page may reduce the drop-off rate during the consideration phase." Structure it as issue → tactic → expected outcome. These hypotheses become the basis for decision-making in subsequent design and development phases.

Pattern 1: Assumption-Based Maps Without Real Data

The most common failure is skipping customer interviews and data collection and building the map around "this is probably what our customer is like." The problem with assumption-based maps is that creators view the customer only through the lens of their own organization and project, resulting in a large gap from actual customer behavior. In particular, the perspective of non-customers — "why did they not choose this service?" — tends to be completely absent.

Remedy: Always conduct customer interviews before building the persona. Interviews with at least 5 existing customers plus 2 non-customers or churned customers (7 total) substantially increase map reliability.

Pattern 2: Maps Created Solely from the Client's Perspective

When clients create the map alone, it tends to be structured around what the company "wants to communicate," rather than what customers actually "want to know" or "feel." Corporate intent ends up being depicted as the customer experience.

Remedy: Have the contractor (web director or UX designer) participate as a facilitator, inserting third-party questions like "Is that really what customers feel?" Customer experience design quality depends on creating an open discussion environment that transcends the client-contractor divide.

Pattern 3: Maps That Are Never Updated After Creation

Changes in market conditions, the emergence of new touchpoints (new social media features, new competitor entries), and shifts in customer demographics cause customer journeys to become outdated over time. Treating a completed map as a "finished deliverable" and never updating it means continuing to plan tactics on premises that are increasingly divorced from reality.

Remedy: When completing the map, define "trigger conditions for the next update." For example: "when the core product or service specification changes significantly," "quarterly scheduled review," or "when the customer satisfaction score changes by 10 points or more from the previous measurement." Make the conditions concrete.

Pattern 4: No Rules for How to Use the Map

Even if a map is created, without documenting "when, by whom, and how it will be used," it becomes wall decoration. If there is no habit of referencing the map in tactic planning meetings, it is effectively as if the map does not exist.

Remedy: Draft a "map utilization protocol" alongside the map. Standardize the process of always referencing the map when considering new tactics — confirming "which phase's issue does this tactic address?" and "which touchpoints does it affect?"

The value of a customer journey map is realized not at the moment of completion, but after operations begin. Systems to make the map function as a living document must be designed from the creation stage.

Sharing and Consensus Building

After the map is completed, present it to stakeholders who were not involved in its creation — executives, development teams, customer support staff, and others. When each department or team member recognizes "our own responsible touchpoints within this map," organizational-wide awareness of customer experience improvement begins to take hold.

Between clients and contractors, it is recommended to create a responsibility assignment table based on the map — clarifying "who leads improvement in which phase." Particularly when the boundary between client and contractor responsibility shifts around the point of lead acquisition, making that boundary explicit on the map serves as prevention for future disputes.

Connecting to the Tactic Roadmap

Translate the issues and tactic hypotheses extracted from the map into a quarterly tactic roadmap. By building the roadmap with explicit labeling of which journey phase each tactic corresponds to — "Q1: SEO reinforcement for the awareness phase," "Q2: content expansion for the consideration phase" — it becomes easier to maintain a whole-system optimization perspective.

After executing tactics, measure their effectiveness and reflect the results in the map. Build a PDCA cycle into map updates, regularly checking "did this tactic improve the emotion curve in the consideration phase?" and "have new issues surfaced?"

Regular Reviews Between Clients and Contractors

During ongoing projects, it is recommended to schedule a customer journey review meeting once per quarter with both clients and contractors participating. In this review, use tactic effectiveness measurement results, customer feedback received, and market environment changes as inputs to update the map. This habit becomes the foundation for embedding a culture of continuous customer experience improvement in the organization.

Rather than treating a customer journey map as a single finished deliverable, positioning it as a tool for ongoing dialogue to deepen customer understanding is the fundamental approach that leads to practical results.

---

References

• Nielsen Norman Group, "Journey Mapping 101" — Fundamentals of customer journey map components and the creation process
• Harvard Business Review, "The Truth About Customer Experience" — Research on the impact of optimizing the entire customer journey on satisfaction
• Interaction Design Foundation, "Customer Journey Maps — Walking a Mile in Your Customer's Shoes" — Practical creation methods and application cases for customer journey maps