discovery-interviews-surveys

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Discovery Interviews & Surveys

发现性访谈与调研

Purpose

目的

Discovery Interviews & Surveys help you learn from users systematically to:

Validate assumptions before investing in building
Discover real problems users experience (not just stated needs)
Understand jobs-to-be-done (what users "hire" your product to do)
Identify pain points and current workarounds
Test concepts and positioning with target audience
Uncover unmet needs that users may not articulate directly

This moves from guessing to evidence-based product decisions.

发现性访谈与调研帮助你系统性地向用户学习，以实现以下目标：

验证假设：在投入开发前验证产品假设
发现真实问题：挖掘用户实际遇到的问题（而非仅用户陈述的需求）
理解用户待办任务：明确用户“雇佣”你的产品来完成的任务（Jobs-to-be-done）
识别痛点与替代方案：找出用户当前的痛点及临时解决办法
测试概念与定位：在目标受众中测试产品概念与定位
发掘未被满足的需求：挖掘用户无法直接表述的潜在需求

这能让产品决策从主观猜测转向基于证据的科学判断。

When to Use

适用场景

Use this skill when:

Pre-build validation: Testing product ideas before development
Problem discovery: Understanding user pain points and workflows
Jobs-to-be-done research: Identifying hiring/firing triggers and desired outcomes
Market research: Understanding target audience, competitive landscape, willingness to pay
Concept testing: Validating positioning, messaging, feature prioritization
Post-launch learning: Understanding adoption barriers, churn reasons, expansion opportunities
Customer satisfaction research: Identifying satisfaction/dissatisfaction drivers
UX research: Mental models, task flows, usability issues
Voice of customer: Gathering qualitative insights for roadmap prioritization

Trigger phrases: "user research", "customer interviews", "surveys", "discovery", "validation study", "voice of customer", "jobs-to-be-done", "JTBD", "user needs"

当你遇到以下场景时，可使用该方法：

开发前验证：在产品开发前测试产品想法
问题挖掘：理解用户痛点与工作流程
用户待办任务研究：识别用户选择或放弃产品的触发因素及期望结果
市场调研：了解目标受众、竞争格局及付费意愿
概念测试：验证产品定位、话术及功能优先级
上线后学习：理解产品 Adoption 障碍、用户流失原因及拓展机会
客户满意度调研：识别影响用户满意度的关键因素
UX 研究：探究用户心智模型、任务流程及可用性问题
客户声音收集：收集定性洞察以指导 roadmap 优先级排序

触发关键词："user research"、"customer interviews"、"surveys"、"discovery"、"validation study"、"voice of customer"、"jobs-to-be-done"、"JTBD"、"user needs"

What Is It?

什么是发现性访谈与调研？

Discovery Interviews & Surveys provide structured approaches to learn from users while avoiding common biases (leading questions, confirmation bias, selection bias).

Key components:

Interview guides: Open-ended questions that reveal problems and context
Survey instruments: Scaled questions for quantitative validation at scale
JTBD probes: Questions focused on hiring/firing triggers and desired outcomes
Bias-avoidance techniques: Past behavior focus, "show me" requests, avoiding hypotheticals
Analysis frameworks: Thematic coding, affinity mapping, statistical analysis

Quick example:

Bad interview question (leading, hypothetical): "Would you pay $49/month for a tool that automatically backs up your files?"

Good interview approach (behavior-focused, problem-discovery):

"Tell me about the last time you lost important files. What happened?"
"What have you tried to prevent data loss? How's that working?"
"Walk me through your current backup process. Show me if possible."
"What would need to change for you to invest time/money in better backup?"

Result: Learn about actual problems, current solutions, willingness to change—not hypothetical preferences.

发现性访谈与调研提供结构化的用户学习方法，同时能避免常见偏见（如诱导性问题、确认偏误、选择偏误）。

核心组成部分：

访谈指南：用于揭示问题与背景信息的开放式问题
调研工具：用于规模化定量验证的分级问题
JTBD 探查问题：聚焦用户选择/放弃产品触发因素及期望结果的问题
避偏技巧：关注过往行为、要求“实际演示”、避免假设性问题
分析框架：主题编码、亲和图分析、统计分析

快速示例：

糟糕的访谈问题（诱导性、假设性）： “你愿意每月支付49美元购买一款自动备份文件的工具吗？”

优质的访谈方式（聚焦行为、挖掘问题）：

“请告诉我你上次丢失重要文件的经历，发生了什么？”
“你尝试过哪些方法防止数据丢失？效果如何？”
“请带我梳理你当前的备份流程，如果可以的话实际演示一下。”
“需要做出哪些改变，你才愿意投入时间/资金使用更好的备份方案？”

结果：了解用户实际遇到的问题、当前解决方案及改变意愿，而非假设性偏好。

Workflow

工作流程

Copy this checklist and track your progress:

Discovery Research Progress:
- [ ] Step 1: Define research objectives and hypotheses
- [ ] Step 2: Identify target participants
- [ ] Step 3: Choose research method (interviews, surveys, or both)
- [ ] Step 4: Design research instruments
- [ ] Step 5: Conduct research and collect data
- [ ] Step 6: Analyze findings and extract insights

Step 1: Define research objectives

Specify what you're trying to learn, key hypotheses to test, success criteria for research, and decision to be informed. See Common Patterns for typical objectives.

Step 2: Identify target participants

Define participant criteria (demographics, behaviors, firmographics), sample size needed, recruitment strategy, and screening questions. For sampling strategies, see resources/methodology.md.

Step 3: Choose research method

Based on objective and constraints:

For deep problem discovery (5-15 participants) → Use resources/template.md for in-depth interviews
For concept testing at scale (50-200+ participants) → Use resources/template.md for quantitative validation
For JTBD research → Use resources/methodology.md for switch interviews
For mixed methods → Interviews for discovery, surveys for validation

Step 4: Design research instruments

Create interview guide or survey with bias-avoidance techniques. Use resources/template.md for structure. Avoid leading questions, focus on past behavior, use "show me" requests. For advanced question design, see resources/methodology.md.

Step 5: Conduct research

Execute interviews (record with permission, take notes) or distribute surveys (pilot test first). Use proper techniques (active listening, follow-up probes, silence for thinking). See Guardrails for critical requirements.

Step 6: Analyze findings

For interviews: thematic coding, affinity mapping, quote extraction. For surveys: statistical analysis, cross-tabs, open-end coding. Create insights document with evidence. Self-assess using resources/evaluators/rubric_discovery_interviews_surveys.json. Minimum standard: Average score ≥ 3.5.

复制以下清单跟踪进度：

发现性研究进度：
- [ ] 步骤1：定义研究目标与假设
- [ ] 步骤2：确定目标参与者
- [ ] 步骤3：选择研究方法（访谈、调研或两者结合）
- [ ] 步骤4：设计研究工具
- [ ] 步骤5：开展研究并收集数据
- [ ] 步骤6：分析研究结果并提取洞察

步骤1：定义研究目标

明确你想要了解的内容、需要验证的核心假设、研究成功标准及将指导的决策。可参考常见模式中的典型目标。

步骤2：确定目标参与者

定义参与者筛选标准（人口统计学、行为特征、企业特征）、所需样本量、招募策略及筛选问题。关于抽样策略，可查看resources/methodology.md。

步骤3：选择研究方法

根据研究目标与约束条件选择：

深度问题挖掘（5-15名参与者） → 使用resources/template.md进行深度访谈
规模化概念测试（50-200+名参与者） → 使用resources/template.md进行定量验证
JTBD 研究 → 使用resources/methodology.md进行转换访谈
混合方法 → 用访谈挖掘问题，用调研验证结论

步骤4：设计研究工具

结合避偏技巧设计访谈指南或调研问卷。可使用resources/template.md的结构。避免诱导性问题，聚焦过往行为，要求“实际演示”。关于高级问题设计，可查看resources/methodology.md。

步骤5：开展研究

执行访谈（需获得许可后录音，同时做笔记）或分发调研问卷（先进行试点测试）。使用恰当的技巧（主动倾听、跟进探查、留出思考沉默时间）。查看注意准则了解关键要求。

步骤6：分析研究结果

访谈分析：主题编码、亲和图分析、提取关键引用。调研分析：统计分析、交叉制表、开放式问题编码。创建包含证据的洞察文档。使用resources/evaluators/rubric_discovery_interviews_surveys.json进行自我评估。最低标准：平均得分≥3.5。

Common Patterns

常见模式

Pattern 1: Problem Discovery Interviews

Objective: Understand user pain points and current workflows
Approach: 8-12 in-depth interviews, open-ended questions, focus on past behavior and actual solutions
Key questions: "Tell me about the last time...", "Walk me through...", "What have you tried?", "How's that working?"
Output: Problem themes, frequency estimates, current workarounds, willingness to change
Example: B2B SaaS discovery—interview potential customers about current tools and pain points

Pattern 2: Jobs-to-be-Done Research

Objective: Identify why users "hire" products and what triggers switching
Approach: Switch interviews with recent adopters or switchers, focus on timeline and context
Key questions: "What prompted you to look?", "What alternatives did you consider?", "What almost stopped you?", "What's different now?"
Output: Hiring triggers, firing triggers, desired outcomes, anxieties, habits
Example: SaaS churn research—interview recent churners about switch to competitor

Pattern 3: Concept Testing (Qualitative)

Objective: Test product concepts, positioning, or messaging before launch
Approach: 10-15 interviews showing concept (mockup, landing page, description), gather reactions
Key questions: "In your own words, what is this?", "Who is this for?", "What would you use it for?", "How much would you expect to pay?"
Output: Comprehension score, perceived value, target audience clarity, pricing anchors
Example: Pre-launch validation—test landing page messaging with target audience

Pattern 4: Survey for Quantitative Validation

Objective: Validate findings from interviews at scale or prioritize features
Approach: 100-500 participants, mix of scaled questions (Likert, ranking) and open-ends
Key questions: Satisfaction scores (CSAT, NPS), feature importance/satisfaction (Kano), usage frequency, demographics
Output: Statistical significance, segmentation, prioritization (importance vs satisfaction matrix)
Example: Product roadmap prioritization—survey 500 users on feature importance

Pattern 5: Continuous Discovery

Objective: Ongoing learning, not one-time project
Approach: Weekly customer conversations (15-30 min), rotating team members, shared notes
Key questions: Varies by current focus (new features, onboarding, expansion, retention)
Output: Continuous insight feed, early problem detection, relationship building
Example: Product team does 3-5 customer calls weekly, logs insights in shared doc

模式1：问题挖掘访谈

目标：理解用户痛点与当前工作流程
方法：8-12次深度访谈，使用开放式问题，聚焦过往行为与实际解决方案
核心问题：“请告诉我上次……的经历”、“带我梳理……的流程”、“你尝试过哪些方法？”、“效果如何？”
输出：问题主题、发生频率估算、当前替代方案、改变意愿
示例：B2B SaaS 产品挖掘——访谈潜在客户了解当前工具及痛点

模式2：用户待办任务（JTBD）研究

目标：识别用户“雇佣”产品的原因及转换触发因素
方法：对近期新用户或转换用户进行转换访谈，聚焦时间线与背景
核心问题：“是什么促使你开始寻找替代方案？”、“你考虑过哪些竞品？”、“什么因素差点让你放弃？”、“现在有什么不同？”
输出：选择触发因素、放弃触发因素、期望结果、顾虑、使用习惯
示例：SaaS 用户流失研究——访谈近期流失用户了解转换至竞品的原因

模式3：定性概念测试

目标：在产品上线前测试产品概念、定位或话术
方法：10-15次访谈，向用户展示产品概念（原型、落地页、描述），收集反馈
核心问题：“用你自己的话描述一下这是什么？”、“这是为谁设计的？”、“你会用它做什么？”、“你预期它的定价是多少？”
输出：理解度评分、感知价值、目标受众清晰度、定价锚点
示例：上线前验证——向目标受众测试落地页话术

模式4：定量验证调研

目标：规模化验证访谈结论或排序功能优先级
方法：100-500名参与者，混合使用分级问题（Likert 量表、排序题）与开放式问题
核心问题：满意度评分（CSAT、NPS）、功能重要性/满意度（Kano 模型）、使用频率、人口统计学信息
输出：统计显著性、用户细分、优先级排序（重要性 vs 满意度矩阵）
示例：产品 roadmap 优先级排序——调研500名用户对功能的重要性评分

模式5：持续发现

目标：持续学习，而非一次性项目
方法：每周与客户进行15-30分钟对话，团队成员轮换参与，共享笔记
核心问题：根据当前关注重点调整（新功能、Onboarding、拓展、留存）
输出：持续洞察信息流、早期问题预警、客户关系维护
示例：产品团队每周进行3-5次客户通话，将洞察记录在共享文档中

Guardrails

注意准则

Critical requirements:

Avoid leading questions: Don't telegraph the "right" answer. Bad: "Don't you think our UI is confusing?" Good: "Walk me through using this feature. What happened?"
Focus on past behavior, not hypotheticals: What people did reveals truth; what they say they'd do is often wrong. Bad: "Would you use this feature?" Good: "Tell me about the last time you needed to do X."
Use "show me" not "tell me": Actual behavior > described behavior. Ask to screen-share, demonstrate current workflow, show artifacts (spreadsheets, tools).
Recruit right participants: Screen carefully. Wrong participants = wasted time. Define inclusion/exclusion criteria, use screening survey.
Sample size appropriate for method: Interviews: 5-15 for themes to emerge. Surveys: 100+ for statistical significance, 30+ per segment if comparing.
Avoid confirmation bias: Actively look for disconfirming evidence. If 9/10 interviews support hypothesis, focus heavily on the 1 that doesn't.
Record and transcribe (with permission): Memory is unreliable. Record interviews, transcribe for analysis. Take notes as backup.
Analyze systematically: Don't cherry-pick quotes that support preferred conclusion. Use thematic coding, count themes, present contradictory evidence.

Common pitfalls:

❌ Asking "would you" questions: Hypotheticals are unreliable. Focus on "have you", "tell me about when", "show me"
❌ Small sample statistical claims: "80% of users want feature X" from 5 interviews is not valid. Interviews = themes, surveys = statistics
❌ Selection bias: Interviewing only enthusiasts or only detractors skews results. Recruit diverse sample
❌ Ignoring non-verbal cues: Hesitation, confusion, workarounds during "show me" reveal truth beyond words
❌ Stopping at surface answers: First answer is often rationalization. Follow up: "Tell me more", "Why did that matter?", "What else?"

关键要求：

避免诱导性问题：不要暗示“正确”答案。错误示例：“你不觉得我们的 UI 很混乱吗？”正确示例：“带我梳理使用这个功能的流程，发生了什么？”
聚焦过往行为，而非假设性问题：用户实际做过的事才是真相；用户说他们会做的事往往不可靠。错误示例：“你会使用这个功能吗？”正确示例：“请告诉我你上次需要完成X任务的经历。”
用“实际演示”替代“口头描述”：实际行为＞口头描述。要求用户屏幕共享、演示当前工作流程、展示相关文件（如表格、工具）。
招募正确的参与者：仔细筛选参与者。错误的参与者=浪费时间。明确定义纳入/排除标准，使用筛选调研。
样本量与方法匹配：访谈：5-15名参与者即可浮现主题。调研：100+名参与者可获得统计显著性；若进行细分对比，每个细分群体需30+名参与者。
避免确认偏误：主动寻找与假设矛盾的证据。如果10次访谈中有9次支持假设，重点关注那1次不支持的访谈。
获得许可后录音并转录：记忆不可靠。获得许可后录制访谈，转录用于分析。同时做笔记作为备份。
系统性分析：不要只挑选支持偏好结论的引用。使用主题编码、统计主题出现次数、呈现矛盾证据。

常见陷阱：

❌ 询问“你会……”类问题：假设性问题不可靠。聚焦“你是否……”、“请告诉我……的经历”、“演示一下……”
❌ 小样本统计结论：从5次访谈得出“80%的用户想要功能X”是无效的。访谈用于挖掘主题，调研用于统计分析
❌ 选择偏误：仅访谈爱好者或批评者会扭曲结果。招募多样化样本
❌ 忽略非语言线索：用户在“演示”时的犹豫、困惑、替代操作，比口头表述更能揭示真相
❌ 停留在表面答案：用户的第一回答往往是合理化解释。跟进追问：“请详细说说”、“为什么这很重要？”、“还有吗？”

Quick Reference

快速参考

Key resources:

resources/template.md: Interview guide template, survey template, JTBD question bank, screening questions
resources/methodology.md: Advanced techniques (JTBD switch interviews, Kano analysis, thematic coding, statistical analysis, continuous discovery)
resources/evaluators/rubric_discovery_interviews_surveys.json: Quality criteria for research design and execution

Typical workflow time:

Interview guide design: 1-2 hours
Conducting 10 interviews: 10-15 hours (including scheduling)
Analysis and synthesis: 4-8 hours
Survey design: 2-4 hours
Survey distribution and collection: 1-2 weeks
Survey analysis: 2-4 hours

When to escalate:

Large-scale quantitative studies (1000+ participants)
Statistical modeling or advanced segmentation
Longitudinal studies (tracking over time)
Ethnographic research (observing in natural setting) → Use resources/methodology.md or consider specialist researcher

Inputs required:

Research objective: What you're trying to learn
Hypotheses (optional): Specific beliefs to test
Target persona: Who to interview/survey
Job-to-be-done (optional): Specific JTBD focus

Outputs produced:

```
discovery-interviews-surveys.md
```
: Complete research plan with interview guide or survey, recruitment criteria, analysis plan, and insights template

核心资源：

resources/template.md：访谈指南模板、调研模板、JTBD 问题库、筛选问题
resources/methodology.md：高级技巧（JTBD 转换访谈、Kano 分析、主题编码、统计分析、持续发现）
resources/evaluators/rubric_discovery_interviews_surveys.json：研究设计与执行的质量标准

典型工作流程耗时：

访谈指南设计：1-2小时
进行10次访谈：10-15小时（含预约时间）
分析与整合：4-8小时
调研设计：2-4小时
调研分发与收集：1-2周
调研分析：2-4小时

何时需升级方法：

大规模定量研究（1000+名参与者）
统计建模或高级用户细分
纵向研究（长期跟踪）
人种学研究（在自然场景中观察） → 使用resources/methodology.md或考虑专业研究员支持

所需输入：

研究目标：你想要了解的内容
假设（可选）：需要验证的特定观点
目标用户画像：访谈/调研对象
用户待办任务（可选）：特定 JTBD 研究方向

产出物：

```
discovery-interviews-surveys.md
```
：完整研究计划，包含访谈指南或调研问卷、招募标准、分析计划及洞察模板