Back to Details

analyzing-customers

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Analyzing Customers

客户分析

This skill performs deep customer analysis using voice of customer research, review mining, sentiment analysis, and behavioral insights to understand customer needs, motivations, and pain points.
本技能通过客户声音研究、评论挖掘、情绪分析和行为洞察，开展深度客户分析，以了解客户需求、动机和痛点。

When to Use This Skill

何时使用本技能

Invoke this skill when the user:
  • Requests customer analysis or voice of customer research
  • Wants to understand customer pain points and needs
  • Asks for buyer persona development
  • Needs sentiment analysis of customer feedback
  • Mentions jobs-to-be-done analysis
  • Wants to analyze customer reviews or feedback
  • Asks about customer motivations or decision drivers
  • Needs to understand customer journey or buying process
当用户有以下需求时，调用本技能：
  • 请求进行客户分析或客户声音研究
  • 想要了解客户痛点与需求
  • 询问用户画像构建方法
  • 需要对客户反馈进行情绪分析
  • 提及Jobs-to-be-Done分析
  • 想要分析客户评论或反馈
  • 询问客户动机或决策驱动因素
  • 需要了解客户旅程或购买流程

Core Analysis Activities

核心分析活动

Review Mining and Sentiment Analysis

评论挖掘与情绪分析

Extract insights from customer reviews:
Steps:
  1. Identify review sources (G2, Capterra, TrustRadius, app stores, Amazon)
  2. Search for product/category reviews using WebSearch
  3. Collect reviews across rating spectrum (1-5 stars)
  4. Extract common themes and patterns
  5. Categorize feedback (features, support, usability, value, etc.)
  6. Analyze sentiment (positive, negative, neutral)
  7. Identify recurring pain points and praise
  8. Quantify frequency of themes
Output Format:
markdown
undefined
从客户评论中提取洞察：
步骤：
  1. 确定评论来源（G2、Capterra、TrustRadius、应用商店、亚马逊）
  2. 使用WebSearch搜索产品/品类相关评论
  3. 收集全评分区间（1-5星）的评论
  4. 提取常见主题与模式
  5. 对反馈进行分类（功能、支持、易用性、价值等）
  6. 分析情绪（正面、负面、中性）
  7. 识别反复出现的痛点与好评点
  8. 量化主题出现频率
输出格式：
markdown
undefined

Review Analysis: [Product/Category]

评论分析：[产品/品类]

Data Summary

数据摘要

  • Reviews analyzed: ~[Number]
  • Sources: [G2, Capterra, etc.]
  • Date range: [Period]
  • Average rating: X.X/5
  • 分析评论数：~[数量]
  • 来源：[G2、Capterra等]
  • 时间范围：[时间段]
  • 平均评分：X.X/5

Sentiment Distribution

情绪分布

  • Positive: XX%
  • Neutral: XX%
  • Negative: XX%
  • 正面：XX%
  • 中性：XX%
  • 负面：XX%

Top Themes (by mention frequency)

热门主题（按提及频率排序）

Positive Themes

正面主题

  1. [Theme] (mentioned in XX% of positive reviews)
    • Key quotes: "[Quote 1]", "[Quote 2]"
    • Insight: [What this tells us]
  2. [Theme] (mentioned in XX% of positive reviews)
    • Key quotes: "[Quote 1]", "[Quote 2]"
    • Insight: [What this tells us]
  1. [主题]（在XX%的正面评论中被提及）
    • 关键引用："[引用1]", "[引用2]"
    • 洞察：[该主题反映的信息]
  2. [主题]（在XX%的正面评论中被提及）
    • 关键引用："[引用1]", "[引用2]"
    • 洞察：[该主题反映的信息]

Negative Themes

负面主题

  1. [Theme] (mentioned in XX% of negative reviews)
    • Key quotes: "[Quote 1]", "[Quote 2]"
    • Impact: [How this affects customers]
    • Severity: [High/Medium/Low]
  2. [Theme] (mentioned in XX% of negative reviews)
    • Key quotes: "[Quote 1]", "[Quote 2]"
    • Impact: [How this affects customers]
    • Severity: [High/Medium/Low]
  1. [主题]（在XX%的负面评论中被提及）
    • 关键引用："[引用1]", "[引用2]"
    • 影响：[对客户的影响]
    • 严重程度：[高/中/低]
  2. [主题]（在XX%的负面评论中被提及）
    • 关键引用："[引用1]", "[引用2]"
    • 影响：[对客户的影响]
    • 严重程度：[高/中/低]

Feature Requests

功能请求

Most requested features not yet available:
  1. [Feature] - XX mentions
  2. [Feature] - XX mentions
最常被提及的未实现功能：
  1. [功能] - XX次提及
  2. [功能] - XX次提及

Use Case Patterns

使用场景模式

How customers actually use the product:
  1. [Use case] - [Description]
  2. [Use case] - [Description]
客户实际使用产品的方式：
  1. [使用场景] - [描述]
  2. [使用场景] - [描述]

Customer Segments in Reviews

评论中的客户细分

  • [Segment 1]: [What they value/complain about]
  • [Segment 2]: [What they value/complain about]
  • [细分群体1]：[他们关注/抱怨的点]
  • [细分群体2]：[他们关注/抱怨的点]

Actionable Insights

可执行洞察

  1. [Insight and recommendation]
  2. [Insight and recommendation]
undefined
  1. [洞察与建议]
  2. [洞察与建议]
undefined

Pain Point Analysis

痛点分析

Systematically identify and prioritize customer pain points:
Steps:
  1. Gather pain point data from multiple sources (reviews, forums, social media, sales calls)
  2. Categorize pain points by type (functional, emotional, financial, social)
  3. Map pain points to customer journey stages
  4. Assess pain severity and frequency
  5. Identify unmet needs vs. underserved needs
  6. Prioritize by impact and opportunity
  7. Connect pain points to solution opportunities
Output Format:
markdown
undefined
系统地识别并优先排序客户痛点：
步骤：
  1. 从多渠道收集痛点数据（评论、论坛、社交媒体、销售通话）
  2. 按类型对痛点分类（功能型、情感型、财务型、社交型）
  3. 将痛点映射到客户旅程阶段
  4. 评估痛点的严重程度与出现频率
  5. 识别未被满足的需求与服务不足的需求
  6. 按影响与机会优先级排序
  7. 将痛点与解决方案机会关联
输出格式：
markdown
undefined

Pain Point Analysis

痛点分析

Critical Pain Points (High Severity × High Frequency)

关键痛点（高严重度 × 高频率）

Pain Point 1: [Name]

痛点1：[名称]

  • Description: [What the pain is]
  • Customer quote: "[Direct quote from customer]"
  • Affected segment: [Who experiences this]
  • Journey stage: [When they experience it]
  • Current workarounds: [How customers cope today]
  • Impact: [Business/productivity/emotional impact]
  • Opportunity: [How a solution could help]
  • Priority: High
  • 描述： [痛点内容]
  • 客户引用： "[客户直接引用]"
  • 受影响群体： [受影响的客户群体]
  • 旅程阶段： [痛点出现的旅程阶段]
  • 当前应对方法： [客户目前的解决方式]
  • 影响： [对业务/生产力/情感的影响]
  • 机会： [解决方案可带来的帮助]
  • 优先级： 高

Pain Point 2: [Name]

痛点2：[名称]

[Same structure]
[相同结构]

Moderate Pain Points (Medium priority)

中度痛点（中等优先级）

[List with brief descriptions]
[简要描述列表]

Pain Point Categories

痛点分类

Functional Pains:
  • Can't achieve desired outcome
  • Solution is too slow/inefficient
  • Too complex or error-prone
Financial Pains:
  • Too expensive
  • Hidden costs
  • Poor ROI
Emotional Pains:
  • Frustrating to use
  • Anxiety-inducing
  • Requires too much effort
Social Pains:
  • Makes them look bad
  • Not trusted by team
  • Poor collaboration
功能型痛点：
  • 无法达成预期结果
  • 解决方案速度过慢/效率低下
  • 过于复杂或容易出错
财务型痛点：
  • 价格过高
  • 隐藏费用
  • 投资回报率低
情感型痛点：
  • 使用时感到沮丧
  • 引发焦虑
  • 需投入过多精力
社交型痛点：
  • 让用户形象受损
  • 不被团队信任
  • 协作不畅

Pain Point Journey Map

痛点旅程地图

Awareness → Consideration → Purchase → Onboarding → Usage → Renewal
    ↓            ↓             ↓           ↓          ↓         ↓
 [Pain A]    [Pain B]      [Pain C]    [Pain D]  [Pain E]  [Pain F]
认知 → 考虑 → 购买 → 入门 → 使用 → 续订
    ↓            ↓             ↓           ↓          ↓         ↓
 [痛点A]    [痛点B]      [痛点C]    [痛点D]  [痛点E]  [痛点F]

Opportunity Sizing

机会规模

  1. [Pain point] → Affects XX% of customers → $XXM opportunity
  2. [Pain point] → Affects XX% of customers → $XXM opportunity
undefined
  1. [痛点] → 影响XX%的客户 → XX美元机会
  2. [痛点] → 影响XX%的客户 → XX美元机会
undefined

Buyer Persona Development

用户画像构建

Create detailed, research-backed buyer personas:
Steps:
  1. Identify distinct customer segments
  2. Research demographic and firmographic data
  3. Analyze behavioral patterns and psychographics
  4. Document goals, motivations, and success criteria
  5. Map pain points and challenges
  6. Identify information sources and influences
  7. Understand decision-making process
  8. Create narrative persona profiles
Persona Template:
markdown
undefined
创建基于研究的详细用户画像：
步骤：
  1. 识别不同的客户细分群体
  2. 研究人口统计与企业统计数据
  3. 分析行为模式与心理特征
  4. 记录目标、动机与成功标准
  5. 映射痛点与挑战
  6. 识别信息来源与影响因素
  7. 了解决策流程
  8. 创建叙事化的用户画像档案
用户画像模板：
markdown
undefined

Persona: [Persona Name]

用户画像：[画像名称]

Profile Snapshot

档案快照

  • Title/Role: [Job title]
  • Industry: [Primary industries]
  • Company Size: [Employee count/revenue]
  • Experience Level: [Years in role/field]
  • Age Range: [If relevant]
  • Location: [If relevant]
  • 职位/角色： [岗位名称]
  • 行业： [主要行业]
  • 企业规模： [员工数量/营收]
  • 经验水平： [岗位/领域从业年限]
  • 年龄范围： [如相关]
  • 所在地： [如相关]

Goals & Motivations

目标与动机

Professional Goals:
  • [Goal 1]: [Why it matters]
  • [Goal 2]: [Why it matters]
Personal Motivations:
  • [Motivation 1]
  • [Motivation 2]
Success Metrics:
  • [How they measure success]
  • [KPIs they care about]
职业目标：
  • [目标1]：[重要性原因]
  • [目标2]：[重要性原因]
个人动机：
  • [动机1]
  • [动机2]
成功指标：
  • [衡量成功的标准]
  • [关注的关键绩效指标]

Pain Points & Challenges

痛点与挑战

Top Challenges:
  1. [Challenge 1]: [Description and impact]
  2. [Challenge 2]: [Description and impact]
  3. [Challenge 3]: [Description and impact]
Daily Frustrations:
  • [Frustration 1]
  • [Frustration 2]
主要挑战：
  1. [挑战1]：[描述与影响]
  2. [挑战2]：[描述与影响]
  3. [挑战3]：[描述与影响]
日常困扰：
  • [困扰1]
  • [困扰2]

Buying Behavior

购买行为

Decision Criteria:
  1. [Criterion 1] - [Priority level]
  2. [Criterion 2] - [Priority level]
  3. [Criterion 3] - [Priority level]
Information Sources:
  • [Source 1: e.g., peer recommendations]
  • [Source 2: e.g., industry blogs]
  • [Source 3: e.g., analyst reports]
Decision Process:
  • Decision-maker or influencer: [Role in decision]
  • Typical buying cycle: [Duration]
  • Key stakeholders involved: [List]
  • Budget authority: [Yes/No/Shared]
Objections & Concerns:
  • [Common objection 1]
  • [Common objection 2]
决策标准：
  1. [标准1] - [优先级]
  2. [标准2] - [优先级]
  3. [标准3] - [优先级]
信息来源：
  • [来源1：如同行推荐]
  • [来源2：如行业博客]
  • [来源3：如分析师报告]
决策流程：
  • 决策者或影响者：[在决策中的角色]
  • 典型购买周期：[时长]
  • 关键利益相关者：[列表]
  • 预算权限：[是/否/共享]
异议与顾虑：
  • [常见异议1]
  • [常见异议2]

Technology & Tools

技术与工具

Current Stack:
  • [Tool 1]
  • [Tool 2]
Tech Savviness: [Low/Medium/High]
当前技术栈：
  • [工具1]
  • [工具2]
技术熟练度： [低/中/高]

Communication Preferences

沟通偏好

  • Preferred channels: [Email, phone, Slack, etc.]
  • Content preferences: [Case studies, demos, technical docs]
  • Tone: [Formal/casual, technical/business-focused]
  • 首选渠道： [邮件、电话、Slack等]
  • 内容偏好： [案例研究、演示、技术文档]
  • 语气： [正式/随意、技术导向/业务导向]

Quote

引用

"[Representative quote that captures their perspective]"
"[能体现其观点的代表性引用]"

How to Reach Them

触达方式

  • Marketing channels: [Where they spend time]
  • Messaging that resonates: [Key themes]
  • Content to create: [Types and topics]
  • 营销渠道：[他们活跃的平台]
  • 有效信息主题：[关键方向]
  • 需创建的内容：[类型与主题]

Red Flags (Anti-Persona Indicators)

警示信号（非目标用户指标）

  • [Indicator that this is NOT a good fit]
  • [Indicator that this is NOT a good fit]
undefined
  • [表明该用户非合适受众的指标]
  • [表明该用户非合适受众的指标]
undefined

Jobs-to-be-Done (JTBD) Analysis

Jobs-to-be-Done（JTBD）分析

Understand what customers are trying to accomplish:
Steps:
  1. Identify the core "job" customers hire your product to do
  2. Map functional, emotional, and social jobs
  3. Document job context and triggers
  4. Identify job steps and desired outcomes
  5. Assess current solutions and alternatives
  6. Find unmet needs in job execution
  7. Prioritize job outcomes by importance and satisfaction
JTBD Framework:
markdown
undefined
了解客户试图完成的任务：
步骤：
  1. 识别客户雇佣产品完成的核心“任务”
  2. 映射功能型、情感型与社交型任务
  3. 记录任务背景与触发因素
  4. 识别任务步骤与预期结果
  5. 评估当前解决方案与替代方案
  6. 发现任务执行中的未被满足需求
  7. 按重要性与满意度对任务结果优先级排序
JTBD框架：
markdown
undefined

Jobs-to-be-Done Analysis

Jobs-to-be-Done分析

Core Job Statement

核心任务陈述

"When [situation], I want to [motivation], so I can [expected outcome]."
Example: "When I need to share project updates with stakeholders, I want to quickly create visual reports, so I can keep everyone aligned without spending hours on formatting."
"当[场景]时，我想要[动机]，以便[预期结果]。"
示例： "当我需要向利益相关者分享项目更新时，我想要快速创建可视化报告，以便无需花费数小时排版就能让所有人保持信息同步。"

Job Type Breakdown

任务类型细分

Functional Job (What task needs to be done)

功能型任务（需完成的具体任务）

  • Main job: [Primary functional goal]
  • Related jobs: [Connected tasks]
  • Success criteria: [How they know it's done well]
  • 核心任务： [主要功能目标]
  • 相关任务： [关联任务]
  • 成功标准： [如何判断任务完成质量]

Emotional Job (How they want to feel)

情感型任务（期望的感受）

  • Desired feelings: [Confident, in control, respected]
  • Feelings to avoid: [Anxious, incompetent, overlooked]
  • 期望感受： [自信、掌控、受尊重]
  • 需避免的感受： [焦虑、无能、被忽视]

Social Job (How they want to be perceived)

社交型任务（期望的他人认知）

  • Desired perception: [Competent, innovative, reliable]
  • Social context: [Team, management, clients]
  • 期望形象： [能干、创新、可靠]
  • 社交背景： [团队、管理层、客户]

Job Context

任务背景

When does this job arise?
  • Trigger: [What causes the need]
  • Frequency: [How often]
  • Duration: [How long it takes currently]
  • Urgency: [Time sensitivity]
Constraints:
  • Time: [Limitations]
  • Resources: [Available tools/budget]
  • Skills: [Required expertise]
任务何时出现？
  • 触发因素：[引发需求的原因]
  • 频率：[出现频次]
  • 当前耗时：[当前完成任务所需时长]
  • 紧急程度：[时间敏感度]
约束条件：
  • 时间：[限制]
  • 资源：[可用工具/预算]
  • 技能：[所需专业知识]

Job Steps & Outcomes

任务步骤与结果

Desired Outcomes at Each Step:
  1. [Step name]
    • Outcome: [What they want to achieve]
    • Current satisfaction: Low/Medium/High
    • Importance: Low/Medium/High
    • Opportunity: [Gap between importance and satisfaction]
  2. [Step name] [Same structure]
各步骤的预期结果：
  1. [步骤名称]
    • 结果：[想要达成的目标]
    • 当前满意度：低/中/高
    • 重要性：低/中/高
    • 机会：[重要性与满意度之间的差距]
  2. [步骤名称] [相同结构]

Current Solutions

当前解决方案

What do they use today?
  1. [Solution 1]
    • What it does well: [Strengths]
    • What it lacks: [Weaknesses]
    • Switching cost: [Barriers to change]
  2. [Solution 2] [Same structure]
Non-consumption:
  • % doing nothing: [XX%]
  • Why: [Reasons for non-consumption]
客户目前使用的方案：
  1. [方案1]
    • 优势：[擅长的方面]
    • 不足：[缺失的功能]
    • 转换成本：[更换的障碍]
  2. [方案2] [相同结构]
未使用任何方案的情况：
  • 未使用占比：[XX%]
  • 原因：[不使用的理由]

Unmet Needs

未被满足的需求

Underserved Outcomes: (High importance, low satisfaction)
  1. Outcome: [Description and opportunity]
  2. Outcome: [Description and opportunity]
Overserved Outcomes: (Low importance, high satisfaction - potential to simplify)
服务不足的结果： （高重要性，低满意度）
  1. [结果]：[描述与机会]
  2. [结果]：[描述与机会]
服务过度的结果： （低重要性，高满意度 - 可简化的方向）
  1. [结果]：[描述]

Solution Implications

解决方案启示

Must-haves:
  • [Critical capability 1]
  • [Critical capability 2]
Differentiators:
  • [Unique approach to job outcome 1]
  • [Unique approach to job outcome 2]
Avoid:
  • [Overserving low-importance outcomes]
undefined
必备功能：
  • [关键能力1]
  • [关键能力2]
差异化优势：
  • [达成任务结果的独特方式1]
  • [达成任务结果的独特方式2]
需避免：
  • [对低重要性结果过度服务]
undefined

Customer Journey Mapping

客户旅程映射

Map the end-to-end customer experience:
Steps:
  1. Define journey scope (which journey to map)
  2. Identify journey stages
  3. Map customer actions at each stage
  4. Document thoughts and emotions
  5. Identify pain points and moments of delight
  6. Note touchpoints and channels
  7. Assess opportunities for improvement
Journey Map Format:
markdown
undefined
绘制端到端的客户体验：
步骤：
  1. 定义旅程范围（需映射的旅程）
  2. 识别旅程阶段
  3. 绘制各阶段的客户行为
  4. 记录客户的想法与情绪
  5. 识别痛点与愉悦时刻
  6. 记录接触点与渠道
  7. 评估改进机会
旅程地图格式：
markdown
undefined

Customer Journey Map: [Journey Name]

客户旅程地图：[旅程名称]

Journey Scope

旅程范围

  • Persona: [Which customer type]
  • Scenario: [Specific use case or goal]
  • Timeframe: [Duration of journey]
  • 用户画像：[对应的客户类型]
  • 场景：[具体使用案例或目标]
  • 时间范围：[旅程时长]

Stage 1: [Stage Name]

阶段1：[阶段名称]

Customer Actions:
  • [Action 1]
  • [Action 2]
Thoughts:
  • "[What they're thinking]"
  • "[Concern or question]"
Emotions: [Happy/Neutral/Frustrated/Anxious]
Touchpoints:
  • [Website, sales call, email, etc.]
Pain Points:
  • [Pain 1]: Severity [High/Med/Low]
  • [Pain 2]: Severity [High/Med/Low]
Opportunities:
  • [Improvement opportunity]
客户行为：
  • [行为1]
  • [行为2]
想法：
  • "[客户的想法]"
  • "[顾虑或疑问]"
情绪： [愉悦/中性/沮丧/焦虑]
接触点：
  • [网站、销售通话、邮件等]
痛点：
  • [痛点1]：严重程度 [高/中/低]
  • [痛点2]：严重程度 [高/中/低]
机会：
  • [改进机会]

Stage 2: [Stage Name]

阶段2：[阶段名称]

[Repeat structure]
[重复结构]

Journey Insights

旅程洞察

Moments of Truth: (Critical moments that make/break the experience)
  1. [Moment]: [Why it's critical]
  2. [Moment]: [Why it's critical]
Drop-off Points:
  • [Stage]: XX% abandon → Why: [Reason]
Delight Opportunities:
  • [Opportunity to exceed expectations]
Quick Wins:
  • [Easy improvement with high impact]
undefined
关键时刻： （决定体验好坏的关键节点）
  1. [时刻]：[为何关键]
  2. [时刻]：[为何关键]
流失点：
  • [阶段]：XX%客户流失 → 原因：[理由]
愉悦机会：
  • [超越客户预期的机会]
快速改进点：
  • [易实施且影响大的改进措施]
undefined

Research Methods

研究方法

Method 1: Review Platform Analysis
  • Platforms: G2, Capterra, TrustRadius, App Store, Google Play, Amazon
  • Approach: Search and analyze recent reviews
  • Focus: Themes, sentiment, feature requests
  • Tools: WebSearch for review content
Method 2: Social Listening
  • Platforms: Reddit, Twitter, LinkedIn, industry forums
  • Approach: Search for product mentions and category discussions
  • Focus: Unfiltered feedback, use cases, workarounds
  • Tools: WebSearch with site-specific queries
Method 3: Community Analysis
  • Sources: Product forums, Slack communities, Discord servers
  • Approach: Identify common questions and issues
  • Focus: Real-world usage patterns and problems
  • Value: Authentic user voice
Method 4: Sales/Support Conversation Mining
  • Sources: CRM notes, support tickets, call transcripts (if available)
  • Approach: Extract patterns from customer conversations
  • Focus: Objections, questions, use cases
  • Note: May require user to provide this data
Method 5: Survey Data Analysis
  • Sources: NPS surveys, customer satisfaction surveys
  • Approach: Analyze quantitative scores and qualitative comments
  • Focus: Satisfaction drivers and detractors
  • Note: User may need to provide survey data
方法1：评论平台分析
  • 平台： G2、Capterra、TrustRadius、App Store、Google Play、亚马逊
  • 方法： 搜索并分析近期评论
  • 重点： 主题、情绪、功能请求
  • 工具： WebSearch获取评论内容
方法2：社交媒体监听
  • 平台： Reddit、Twitter、LinkedIn、行业论坛
  • 方法： 搜索产品提及与品类讨论
  • 重点： 真实反馈、使用场景、应对方法
  • 工具： 带站点特定查询的WebSearch
方法3：社区分析
  • 来源： 产品论坛、Slack社区、Discord服务器
  • 方法： 识别常见问题与议题
  • 重点： 真实使用模式与问题
  • 价值： 真实用户声音
方法4：销售/支持对话挖掘
  • 来源： CRM记录、支持工单、通话记录（如可用）
  • 方法： 从客户对话中提取模式
  • 重点： 异议、疑问、使用场景
  • 注意： 可能需要用户提供相关数据
方法5：调查数据分析
  • 来源： NPS调查、客户满意度调查
  • 方法： 分析量化评分与定性评论
  • 重点： 满意度驱动因素与 detractors
  • 注意： 可能需要用户提供调查数据

Analysis Patterns

分析模式

Pattern 1: New Market Customer Research
  • When: Entering new market or launching new product
  • Approach:
    1. Define target customer hypotheses
    2. Mine reviews of competitor/alternative products
    3. Analyze community discussions
    4. Develop initial personas
    5. Create JTBD framework
    6. Identify top pain points
  • Output: Customer research brief with personas and JTBD
Pattern 2: Product-Market Fit Assessment
  • When: Validating product-market fit
  • Approach:
    1. Analyze review sentiment and themes
    2. Identify must-have vs. nice-to-have features
    3. Map pain points to product capabilities
    4. Assess job outcome satisfaction
    5. Calculate NPS/satisfaction proxies from reviews
  • Output: PMF assessment with recommendations
Pattern 3: Feature Prioritization Research
  • When: Deciding what to build next
  • Approach:
    1. Mine feature requests from reviews
    2. Analyze pain points by frequency and severity
    3. Map to JTBD outcomes (importance vs. satisfaction)
    4. Assess competitive feature gaps
    5. Prioritize by customer impact
  • Output: Prioritized feature opportunity list
Pattern 4: Churn Risk Analysis
  • When: Understanding why customers leave
  • Approach:
    1. Analyze negative reviews for churn signals
    2. Identify switching triggers
    3. Map to customer journey stages
    4. Assess competitive alternatives mentioned
    5. Recommend retention strategies
  • Output: Churn driver analysis and mitigation plan
Pattern 5: Segment-Specific Analysis
  • When: Understanding differences between customer segments
  • Approach:
    1. Filter feedback by segment (enterprise vs. SMB, industry, etc.)
    2. Compare pain points across segments
    3. Analyze differing needs and priorities
    4. Create segment-specific personas
    5. Recommend segment strategies
  • Output: Segment comparison and strategy recommendations
模式1：新市场客户研究
  • 适用场景： 进入新市场或推出新产品
  • 方法：
    1. 定义目标客户假设
    2. 挖掘竞品/替代产品的评论
    3. 分析社区讨论
    4. 构建初始用户画像
    5. 创建JTBD框架
    6. 识别核心痛点
  • 输出： 包含用户画像与JTBD的客户研究简报
模式2：产品市场契合度评估
  • 适用场景： 验证产品市场契合度
  • 方法：
    1. 分析评论情绪与主题
    2. 识别必备功能与锦上添花功能
    3. 将痛点映射到产品能力
    4. 评估任务结果满意度
    5. 从评论中计算NPS/满意度代理指标
  • 输出： 产品市场契合度评估报告与建议
模式3：功能优先级研究
  • 适用场景： 决定下一步开发方向
  • 方法：
    1. 从评论中挖掘功能请求
    2. 按频率与严重度分析痛点
    3. 映射到JTBD结果（重要性vs满意度）
    4. 评估竞品功能差距
    5. 按客户影响优先级排序
  • 输出： 优先级排序的功能机会列表
模式4：流失风险分析
  • 适用场景： 了解客户流失原因
  • 方法：
    1. 分析负面评论中的流失信号
    2. 识别转换触发因素
    3. 映射到客户旅程阶段
    4. 评估提及的竞品替代方案
    5. 推荐留存策略
  • 输出： 流失驱动因素分析与缓解计划
模式5：细分群体特定分析
  • 适用场景： 了解不同客户细分群体的差异
  • 方法：
    1. 按细分群体过滤反馈（企业vs中小企业、行业等）
    2. 比较不同群体的痛点
    3. 分析不同群体的需求与优先级差异
    4. 创建细分群体特定用户画像
    5. 推荐细分群体策略
  • 输出： 细分群体对比与策略建议

Validation Checklist

验证清单

Before completing customer analysis:
  • Multiple data sources consulted
  • Sufficient volume of feedback analyzed (50+ reviews/data points)
  • Themes validated across sources
  • Quantitative data (frequency, percentages) included
  • Direct customer quotes included
  • Personas based on real patterns, not assumptions
  • JTBD statements validated against customer language
  • Pain points prioritized by impact
  • Actionable insights and recommendations provided
  • Segment differences identified
  • Journey map reflects actual customer experience
完成客户分析前需确认：
  • 已参考多数据源
  • 已分析足够数量的反馈（50+评论/数据点）
  • 主题已跨数据源验证
  • 包含量化数据（频率、百分比）
  • 包含客户直接引用
  • 用户画像基于真实模式而非假设
  • JTBD陈述已与客户语言验证
  • 痛点已按影响优先级排序
  • 提供可执行洞察与建议
  • 已识别细分群体差异
  • 旅程地图反映真实客户体验

Examples

示例

Example 1: Review Mining for SaaS Product
Input: "Analyze customer reviews for project management software to understand pain points"
Process:
  1. Search G2, Capterra for "project management software" reviews
  2. Collect 100+ recent reviews across top products
  3. Categorize feedback themes (ease of use, features, pricing, support)
  4. Extract specific pain points and praise
  5. Calculate theme frequency and sentiment
  6. Identify feature gaps and requests
  7. Develop actionable insights
Output: Comprehensive review analysis with top pain points, feature requests, sentiment breakdown, and product recommendations
Example 2: Buyer Persona Development
Input: "Create buyer personas for our DevOps monitoring tool"
Process:
  1. Analyze reviews to identify distinct user types
  2. Research job titles and roles in DevOps
  3. Extract goals and challenges from feedback
  4. Identify decision criteria and buying process
  5. Map typical tech stack and environment
  6. Document communication preferences
  7. Create 2-3 distinct personas
Output: Detailed buyer personas with goals, pain points, buying behavior, and how to reach them
示例1：SaaS产品评论挖掘
输入："分析项目管理软件的客户评论以了解痛点"
流程：
  1. 在G2、Capterra搜索“项目管理软件”评论
  2. 收集100+近期主流产品评论
  3. 对反馈主题分类（易用性、功能、定价、支持）
  4. 提取具体痛点与好评点
  5. 计算主题频率与情绪
  6. 识别功能差距与请求
  7. 生成可执行洞察
输出：包含核心痛点、功能请求、情绪分布与产品建议的全面评论分析报告
示例2：用户画像构建
输入："为我们的DevOps监控工具创建用户画像"
流程：
  1. 分析评论以识别不同用户类型
  2. 研究DevOps领域的职位与角色
  3. 从反馈中提取目标与挑战
  4. 识别决策标准与购买流程
  5. 映射典型技术栈与环境
  6. 记录沟通偏好
  7. 创建2-3个差异化用户画像
输出：包含目标、痛点、购买行为与触达方式的详细用户画像

Additional Notes

补充说明

  • Voice of customer research is ongoing, not one-time
  • Review platforms may require filtering out fake/incentivized reviews
  • Look for both stated needs (explicit) and latent needs (implicit)
  • Combine quantitative data (ratings, frequency) with qualitative insights (quotes)
  • Validate assumptions against real customer data
  • Update personas regularly as market evolves
  • Use direct customer language in insights and personas
  • Combine with competitive-intelligence to understand why customers choose alternatives
  • Link to analyzing-pricing to understand willingness to pay
  • 客户声音研究是持续的过程，而非一次性活动
  • 评论平台可能需要过滤虚假/激励性评论
  • 需同时关注明确需求（显性）与潜在需求（隐性）
  • 结合量化数据（评分、频率）与定性洞察（引用）
  • 用真实客户数据验证假设
  • 随市场变化定期更新用户画像
  • 在洞察与用户画像中使用客户原话
  • 结合竞争情报了解客户选择替代方案的原因
  • 可关联定价分析以了解客户支付意愿