product-discovery

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Product Discovery

产品发现

Strategic user research and problem validation expertise — from interview techniques and JTBD to opportunity sizing and insight synthesis.

战略性用户研究与问题验证专业指南——涵盖访谈技巧、JTBD框架、机会规模评估到洞察整合全流程。

Philosophy

理念

Great products start with great problems. Discovery is how you find problems worth solving for people who will pay.

The best product discovery:

Talk to users, not stakeholders — Customers know their problems, not solutions
Validate problems before solutions — Build the right thing, then build it right
Quantify and qualify — Numbers tell you what, conversations tell you why
Continuous over batched — Weekly habits beat quarterly projects

优秀的产品始于值得解决的问题。产品发现就是找到那些用户愿意为之付费的问题的过程。

最佳产品发现原则：

与用户对话，而非利益相关者——客户了解自己的问题，而非解决方案
先验证问题，再考虑解决方案——先做正确的事，再把事做正确
量化与定性结合——数据告诉你“是什么”，对话告诉你“为什么”
持续发现优于批量式发现——每周的习惯胜过季度项目

How This Skill Works

本技能的运作方式

When invoked, apply the guidelines in

rules/

organized by:

```
research-*
```
— User interview techniques, survey design, research ops
```
discovery-*
```
— Problem discovery, JTBD framework, validation
```
analysis-*
```
— Synthesis, segmentation, competitive analysis
```
testing-*
```
— Prototype testing, usability testing

调用本技能时，请遵循

rules/

目录下的指南，这些指南分为以下类别：

```
research-*
```
— 用户访谈技巧、调研设计、研究运营
```
discovery-*
```
— 问题发现、JTBD框架、验证
```
analysis-*
```
— 洞察整合、客户细分、竞品分析
```
testing-*
```
— 原型测试、可用性测试

Core Frameworks

核心框架

Discovery Process

产品发现流程

Phase	Activities	Outputs
Explore	Interviews, observation, data mining	Problem space map
Validate	Problem interviews, surveys, experiments	Validated problems
Prioritize	Opportunity scoring, segmentation	Prioritized roadmap
Test	Prototype testing, usability studies	Solution validation

阶段	活动	产出
探索	用户访谈、观察、数据挖掘	问题空间地图
验证	问题访谈、调研、实验	已验证的问题
优先级排序	机会评分、客户细分	优先级路线图
测试	原型测试、可用性研究	解决方案验证

Jobs-to-be-Done Framework

Jobs-to-be-Done（JTBD）框架

                    ┌─────────────────────┐
                    │    FUNCTIONAL JOB   │
                    │   (What they do)    │
                    └──────────┬──────────┘
                               │
              ┌────────────────┼────────────────┐
              │                │                │
              ▼                ▼                ▼
       ┌──────────┐     ┌──────────┐     ┌──────────┐
       │ EMOTIONAL│     │  SOCIAL  │     │ CONTEXT  │
       │   JOB    │     │   JOB    │     │ (When/   │
       │ (Feel)   │     │ (Appear) │     │  Where)  │
       └──────────┘     └──────────┘     └──────────┘

                    ┌─────────────────────┐
                    │    FUNCTIONAL JOB   │
                    │   (What they do)    │
                    └──────────┬──────────┘
                               │
              ┌────────────────┼────────────────┐
              │                │                │
              ▼                ▼                ▼
       ┌──────────┐     ┌──────────┐     ┌──────────┐
       │ EMOTIONAL│     │  SOCIAL  │     │ CONTEXT  │
       │   JOB    │     │   JOB    │     │ (When/   │
       │ (Feel)   │     │ (Appear) │     │  Where)  │
       └──────────┘     └──────────┘     └──────────┘

Opportunity Scoring (OST)

机会评分（OST）

Factor	Weight	Description
Importance	40%	How important is this job to the customer?
Satisfaction	30%	How satisfied are they with current solutions?
Frequency	20%	How often do they encounter this problem?
Willingness to Pay	10%	Will they pay to solve this?

Opportunity Score = Importance + max(Importance - Satisfaction, 0)

因素	权重	描述
重要性	40%	这项工作对客户有多重要？
满意度	30%	客户对现有解决方案的满意度如何？
频率	20%	客户多久会遇到一次这个问题？
付费意愿	10%	客户是否愿意付费解决这个问题？

机会评分 = 重要性 + max(重要性 - 满意度, 0)

Research Method Selection

研究方法选择

┌─────────────────────────────────────────────────────────────┐
│                   GENERATIVE RESEARCH                       │
│              (Discover unknown unknowns)                    │
│  ┌───────────┐  ┌───────────┐  ┌───────────┐               │
│  │Contextual │  │ Discovery │  │ Diary    │               │
│  │ Inquiry   │  │ Interviews│  │ Studies  │               │
│  └───────────┘  └───────────┘  └───────────┘               │
├─────────────────────────────────────────────────────────────┤
│                   EVALUATIVE RESEARCH                       │
│              (Validate known hypotheses)                    │
│  ┌───────────┐  ┌───────────┐  ┌───────────┐               │
│  │ Usability │  │  A/B      │  │ Prototype │               │
│  │ Testing   │  │  Testing  │  │ Testing   │               │
│  └───────────┘  └───────────┘  └───────────┘               │
├─────────────────────────────────────────────────────────────┤
│                   QUANTITATIVE RESEARCH                     │
│              (Measure and prioritize)                       │
│  ┌───────────┐  ┌───────────┐  ┌───────────┐               │
│  │  Surveys  │  │ Analytics │  │ Card      │               │
│  │           │  │  Review   │  │ Sorting   │               │
│  └───────────┘  └───────────┘  └───────────┘               │
└─────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────┐
│                   GENERATIVE RESEARCH                       │
│              (Discover unknown unknowns)                    │
│  ┌───────────┐  ┌───────────┐  ┌───────────┐               │
│  │Contextual │  │ Discovery │  │ Diary    │               │
│  │ Inquiry   │  │ Interviews│  │ Studies  │               │
│  └───────────┘  └───────────┘  └───────────┘               │
├─────────────────────────────────────────────────────────────┤
│                   EVALUATIVE RESEARCH                       │
│              (Validate known hypotheses)                    │
│  ┌───────────┐  ┌───────────┐  ┌───────────┐               │
│  │ Usability │  │  A/B      │  │ Prototype │               │
│  │ Testing   │  │  Testing  │  │ Testing   │               │
│  └───────────┘  └───────────┘  └───────────┘               │
├─────────────────────────────────────────────────────────────┤
│                   QUANTITATIVE RESEARCH                     │
│              (Measure and prioritize)                       │
│  ┌───────────┐  ┌───────────┐  ┌───────────┐               │
│  │  Surveys  │  │ Analytics │  │ Card      │               │
│  │           │  │  Review   │  │ Sorting   │               │
│  └───────────┘  └───────────┘  └───────────┘               │
└─────────────────────────────────────────────────────────────┘

Customer Segmentation Matrix

客户细分矩阵

Dimension	Consumer (B2C)	Business (B2B)
Demographics	Age, income, location	Company size, industry, revenue
Behavior	Usage patterns, purchase history	Buying process, tech stack
Psychographics	Values, lifestyle, attitudes	Company culture, risk tolerance
Needs	Problems, goals, aspirations	Business outcomes, KPIs

维度	消费者（B2C）	企业（B2B）
人口统计	年龄、收入、地域	公司规模、行业、营收
行为特征	使用模式、购买历史	采购流程、技术栈
心理特征	价值观、生活方式、态度	企业文化、风险容忍度
需求	问题、目标、愿景	业务成果、关键绩效指标（KPIs）

Continuous Discovery Cadence

持续发现节奏

Weekly:
├── 2-3 customer interviews
├── Review analytics/feedback
└── Update opportunity backlog

Monthly:
├── Synthesis session
├── Prioritization review
└── Stakeholder alignment

Quarterly:
├── Deep-dive research sprint
├── Competitive analysis refresh
└── Segment review

Weekly:
├── 2-3 customer interviews
├── Review analytics/feedback
└── Update opportunity backlog

Monthly:
├── Synthesis session
├── Prioritization review
└── Stakeholder alignment

Quarterly:
├── Deep-dive research sprint
├── Competitive analysis refresh
└── Segment review

Interview Quick Reference

访谈速查指南

Interview Type	When to Use	Key Questions
Discovery	Exploring problem space	"Tell me about the last time..."
Problem	Validating specific pain	"How painful is this 1-10? Why?"
Solution	Testing concepts	"Would this solve your problem?"
JTBD	Understanding motivation	"What were you trying to accomplish?"
Usability	Testing interfaces	"What do you expect to happen?"

访谈类型	使用场景	核心问题
发现型访谈	探索问题空间	“告诉我你最近一次遇到……的经历”
问题验证型访谈	验证特定痛点	“这个问题的痛苦程度是1-10的几分？为什么？”
解决方案测试型访谈	测试概念	“这个方案能解决你的问题吗？”
JTBD访谈	理解动机	“你当时想要达成什么目标？”
可用性测试访谈	测试界面	“你期望这里会发生什么？”

Anti-Patterns

反模式

Solution-first discovery — Falling in love with solutions before validating problems
Leading the witness — Asking questions that suggest desired answers
Confirmation bias — Only hearing what supports your hypothesis
Sample of one — Making decisions from a single interview
Proxy research — Asking salespeople instead of customers
Feature requests as research — Users ask for features, not problems
Analysis paralysis — Researching forever, never deciding
HiPPO-driven — Highest Paid Person's Opinion overriding data

先解决方案后发现——在验证问题之前就沉迷于解决方案
诱导受访者——提出暗示期望答案的问题
确认偏差——只听取支持自己假设的内容
单一样本决策——仅凭一次访谈就做出决策
代理研究——询问销售人员而非直接询问客户
将功能请求视为研究结果——用户提出的是功能需求，而非问题本身
分析瘫痪——无休止地研究，从不做决策
HiPPO驱动——职位最高者的意见凌驾于数据之上