biz-customer-journey

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Customer Journey Mapping

Customer Journey Mapping（客户旅程映射）

Overview

概述

Customer Journey Mapping visualizes the entire experience a customer has with a brand — from first awareness through post-purchase advocacy. It identifies touchpoints, emotions, pain points, and opportunities at each stage. The goal is to find and fix where customers get stuck, frustrated, or leave.

Customer Journey Mapping 可视化客户与品牌的整个体验过程——从最初的认知阶段到购买后的拥护阶段。它会识别每个阶段的触点、情绪、痛点以及改进机会。其目标是找出并解决客户遇到阻碍、感到沮丧或选择离开的环节。

When to Use

使用场景

Trigger conditions:

User wants to improve conversion rates across the funnel
User needs to understand where customers drop off
User designing or redesigning a customer experience
User asks "where are we losing customers?" or "what's the user experience like?"

When NOT to use:

For market segmentation → use STP
For product feature decisions → use Jobs to Be Done
For one-time strategic analysis → use SWOT

触发条件：

用户希望提升转化漏斗各环节的转化率
用户需要了解客户在哪个环节流失
用户正在设计或重新设计客户体验
用户询问“我们在哪里流失客户？”或“用户体验是什么样的？”

不适用场景：

市场细分 → 使用STP模型
产品功能决策 → 使用Jobs to Be Done（待办任务）框架
一次性战略分析 → 使用SWOT分析

Framework

核心法则

IRON LAW: Map the Customer's Reality, Not Your Ideal

The journey map must reflect what customers ACTUALLY experience, not what
you designed or intended. If customers Google your brand and find negative
reviews (reality), don't map "customer visits our website" (ideal).

Base the map on data: analytics, customer interviews, support tickets,
heatmaps — not internal assumptions.

IRON LAW: Every Touchpoint Needs an Emotion

A journey map without emotions is a process diagram. At every touchpoint,
note the customer's emotional state: confident, confused, frustrated,
delighted. Emotions predict behavior better than process steps.

IRON LAW: Map the Customer's Reality, Not Your Ideal

旅程图必须反映客户的**实际**体验，而非你设计或期望的体验。如果客户通过谷歌搜索你的品牌时看到负面评价（实际情况），就不要绘制“客户访问我们的官网”（理想情况）。

旅程图需基于数据：分析数据、客户访谈、支持工单、热力图——而非内部假设。

IRON LAW: Every Touchpoint Needs an Emotion

没有情绪的旅程图只是流程示意图。在每个触点，都要记录客户的情绪状态：自信、困惑、沮丧、愉悦。情绪比流程步骤更能预测客户行为。

The Five Stages

五个阶段

1. Awareness — Customer realizes they have a need or discovers your brand

Touchpoints: ads, social media, word-of-mouth, search results, content
Key question: "How do they first encounter us?"

2. Consideration — Customer evaluates options and compares alternatives

Touchpoints: website, reviews, comparisons, demos, sales conversations
Key question: "What information do they seek and where?"

3. Decision — Customer chooses and purchases

Touchpoints: checkout, pricing page, sales closing, contract signing
Key question: "What friction exists at the purchase moment?"

4. Usage — Customer uses the product/service

Touchpoints: onboarding, product interaction, support, documentation
Key question: "Does the experience match the promise?"

5. Advocacy — Customer recommends (or warns against) the brand

Touchpoints: reviews, referrals, social sharing, community
Key question: "What triggers them to recommend us — or not?"

1. 认知（Awareness）——客户意识到自身需求或发现你的品牌

触点：广告、社交媒体、口碑传播、搜索结果、内容营销
核心问题：“客户最初是如何接触到我们的？”

2. 考虑（Consideration）——客户评估选项并对比竞品

触点：官网、评论、对比内容、产品演示、销售沟通
核心问题：“客户会寻找哪些信息，以及在哪里寻找？”

3. 决策（Decision）——客户选择并完成购买

触点：结账页面、定价页、销售成交、合同签署
核心问题：“购买环节存在哪些摩擦？”

4. 使用（Usage）——客户使用产品/服务

触点：新用户引导、产品交互、客服支持、文档资料
核心问题：“实际体验是否符合承诺？”

5. 拥护（Advocacy）——客户推荐（或警告他人远离）你的品牌

触点：评论、推荐、社交分享、社区互动
核心问题：“是什么触发客户推荐我们——或不推荐？”

Step 1: Define the Persona

步骤1：定义Persona（用户画像）

Who is this journey for? Use the target segment from STP:

Name, demographics, goals, pain points
The more specific the persona, the more actionable the map

该旅程是针对哪类用户？使用STP模型中的目标细分群体：

姓名、人口统计信息、目标、痛点
用户画像越具体，旅程图的可操作性越强

Step 2: Map Touchpoints per Stage

步骤2：按阶段映射触点

For each stage, list:

Touchpoints: Every interaction point (physical, digital, human)
Actions: What the customer does
Emotions: How the customer feels (😊 positive / 😐 neutral / 😤 negative)
Pain points: What frustrates or blocks them
Opportunities: How to improve the experience

针对每个阶段，列出：

触点（Touchpoints）：所有交互点（实体、数字、人工）
行动：客户的行为
情绪：客户的感受（😊 正面 / 😐 中立 / 😤 负面）
痛点：让客户感到沮丧或受阻的问题
改进机会：如何优化体验

Step 3: Identify Moments of Truth

步骤3：识别关键时刻（Moments of Truth）

Find the 2-3 critical moments that disproportionately impact the overall experience:

First impression: The first touchpoint sets expectations
Friction peak: The highest-pain-point moment
Delight opportunity: Where a small improvement creates outsized positive impact

找出2-3个对整体体验影响极大的关键瞬间：

第一印象：首个触点会设定客户的期望
摩擦峰值：痛点最突出的时刻
愉悦机会点：小改进就能带来巨大正面影响的环节

Step 4: Prioritize Improvements

步骤4：优先改进事项

Rank improvements by: Impact on customer satisfaction × Feasibility × Cost. Fix the highest-impact pain points first.

按照“客户满意度影响 × 可行性 × 成本”的维度对改进事项排序。优先解决影响最大的痛点。

Output Format

输出格式

markdown

undefined

markdown

undefined

Customer Journey Map: {Product/Service}

Customer Journey Map: {产品/服务名称}

Persona

Name: {persona name}
Profile: {segment description}
Goal: {what they're trying to achieve}

Name: {用户画像名称}
Profile: {细分群体描述}
Goal: {用户的核心目标}

Journey Map

Stage	Touchpoints	Actions	Emotion	Pain Points	Opportunities
Awareness	{list}	{what they do}	😊/😐/😤	{friction}	{improvement}
Consideration	...	...	...	...	...
Decision	...	...	...	...	...
Usage	...	...	...	...	...
Advocacy	...	...	...	...	...

阶段	触点	行动	情绪	痛点	改进机会
Awareness	{列表}	{客户行为}	😊/😐/😤	{摩擦点}	{改进方案}
Consideration	...	...	...	...	...
Decision	...	...	...	...	...
Usage	...	...	...	...	...
Advocacy	...	...	...	...	...

Moments of Truth

{moment} — {why this is critical}
{moment} — {why this is critical}

{关键时刻} — {为何至关重要}
{关键时刻} — {为何至关重要}

Priority Improvements

{Stage} → {specific improvement} — Impact: High, Effort: Low
...

undefined

{阶段} → {具体改进措施} — 影响：高，难度：低
...

undefined

Examples

示例

Correct Application

正确应用

Scenario: Journey for a Taiwanese food delivery app (persona: 30-year-old office worker ordering lunch)

Stage	Touchpoints	Emotion	Pain Point
Awareness	Colleague mentions app during lunch discussion	😊 Curious	None — organic discovery
Consideration	Downloads app, browses restaurants, reads reviews	😐 → 😤	Too many choices, no "nearby + fast" filter
Decision	Selects restaurant, adds items, sees delivery fee + minimum order	😤	Delivery fee NT$60 feels expensive for a NT$120 lunch; minimum order forces buying more than needed
Usage	Waits for delivery, receives food, eats	😊 → 😐	Food arrives in 35 min (app said 25), packaging leaked
Advocacy	Doesn't refer friends	😐	No referral incentive; experience was "okay, not great"

Moment of Truth: Decision stage — the delivery fee shock causes 40% cart abandonment (data-backed ✓).

场景： 台湾外卖应用的客户旅程（用户画像：30岁办公室职员，订购午餐）

阶段	触点	情绪	痛点
Awareness	午餐时同事提及该应用	😊 好奇	无——自然发现
Consideration	下载应用、浏览餐厅、查看评论	😐 → 😤	选项过多，没有“附近+快速送达”筛选器
Decision	选择餐厅、添加餐品、看到配送费+最低起送额	😤	120台币的午餐需支付60台币配送费，感觉太贵；最低起送额迫使购买超出需求的餐品
Usage	等待配送、收到餐品、用餐	😊 → 😐	餐品35分钟送达（应用显示25分钟），包装漏汁
Advocacy	未推荐给朋友	😐	无推荐激励；体验“一般，不算好”

关键时刻：决策阶段——配送费的冲击导致40%的购物车弃单（有数据支持 ✓）。

Incorrect Application

错误应用

What went wrong:

Map shows "Customer visits website → Customer signs up → Customer makes purchase" → This is a process flow, not a journey map. No emotions, no pain points. Violates Iron Law: every touchpoint needs an emotion.
Awareness stage shows "Customer sees our billboard campaign" when the company doesn't have billboards → Mapping the ideal, not reality. Violates Iron Law: map reality.

问题所在：

旅程图显示“客户访问官网 → 客户注册 → 客户完成购买”——这是流程流程图，而非旅程图。没有情绪、没有痛点，违反了核心法则：每个触点都需要记录情绪。
认知阶段显示“客户看到我们的广告牌广告”，但公司并未投放广告牌——绘制的是理想情况，而非实际情况，违反了核心法则：要映射实际体验。

Gotchas

注意事项

Backstage vs frontstage: Customers don't see your internal processes. Map what the customer experiences, not your operations. "Order routed to kitchen" is backstage; "Customer sees 'preparing your order' notification" is frontstage.
Multiple personas = multiple maps: Different segments have different journeys. A B2B enterprise buyer's journey is completely different from a self-serve SMB user. Don't combine them.
Post-purchase is often ignored: Most teams map Awareness → Decision thoroughly but skip Usage and Advocacy. Retention and referral happen post-purchase.
Data over intuition: "We think customers feel frustrated at checkout" is a hypothesis. "Cart abandonment rate is 65% at the delivery fee screen" is evidence. Use data wherever possible.
Journey maps expire: Customer behavior changes. A map from 2023 may be obsolete by 2025. Revisit quarterly for fast-moving products.

后台流程 vs 前台体验：客户看不到你的内部流程。要映射客户的实际体验，而非你的运营流程。“订单派送至厨房”是后台流程；“客户看到‘正在准备您的订单’通知”是前台体验。
多用户画像 = 多旅程图：不同细分群体的旅程完全不同。B2B企业买家的旅程与自助式SMB用户的旅程截然不同，不要将它们合并。
购买后环节常被忽略：大多数团队会详细绘制认知→决策阶段，但忽略使用和拥护阶段。客户留存和推荐都发生在购买后。
数据优先于直觉：“我们认为客户在结账时感到沮丧”是假设；“配送费页面的购物车弃单率为65%”是证据。尽可能使用数据。
旅程图会过期：客户行为会变化。2023年的旅程图到2025年可能就过时了。对于快速迭代的产品，需每季度重新审视。

References

参考资料

For service blueprint extension (adding backstage operations), see
```
references/service-blueprint.md
```

如需扩展服务蓝图（添加后台运营流程），请查看
```
references/service-blueprint.md
```