关于 problem-interview
problem-interview 是一项用于开展问题发现访谈的技能,面向验证客户问题是否真实、严重且值得解决的产品团队。它帮助准备非引导式访谈、了解现有解决方式,并分析问题的频率与影响。
主要功能
- 01制定问题假设与访谈脚本
- 02设计开放式非引导问题
- 03评估问题严重程度与频率
- 04了解受访者现有解决方式
- 05分析访谈证据并决定后续行动
适用场景
- 01在提出解决方案前验证问题
- 02探索新客户群体的痛点
- 03比较不同问题的优先级
安装
复制下面的命令,在终端中运行。
npx skills add https:/ / github.com/ guia-matthieu/ clawfu-skills --skill problem-interview安装后在 Claude Code 中输入/problem-interview确认已加载。
详细介绍
问题访谈
在开始构建任何东西之前,先验证你想解决的问题确实存在、令人痛苦且值得解决。掌握 Cindy Alvarez 的结构化问题探索访谈方法。
何时使用此技能
- 解决方案访谈之前,确认问题确实存在
- 客户探索早期阶段,了解问题领域
- 调整方向时,寻找值得解决的新问题
- 拓展市场时,了解新细分市场中的问题
- 确定功能优先级时,验证哪些问题最重要
- 测试假设时,验证或否定关于问题的假设
方法论基础
| 方面 | 详情 |
|---|---|
| 来源 | Cindy Alvarez - “Lean Customer Development”(2014 年) |
| 核心原则 | “问题访谈能帮助你在投入解决方案之前了解问题领域。你不是在推销,而是在学习。” |
| 为何重要 | 大多数初创公司失败,是因为它们解决的问题并没有重要到让人足够在意。问题访谈可以避免为并非问题的事构建解决方案。 |
Claude 的职责与你的决定
| Claude 的职责 | 你的决定 |
|---|---|
| 规划制作工作流 | 最终创意方向 |
| 提出技术方法 | 设备和工具选择 |
| 创建模板和检查清单 | 质量标准 |
| 确定最佳实践 | 品牌/风格决策 |
| 生成脚本大纲 | 最终脚本审批 |
此技能的功能
- 规划问题探索 - 以系统化方式了解痛点
- 判断问题严重程度 - 区分“锦上添花”和“必须解决”
- 发现现有解决方案 - 了解人们目前的做法
- 验证问题出现频率 - 这个问题多久出现一次?
- 查明问题情境 - 问题在何时何地发生?
- 生成解决方案线索 - 理想的情况会是什么样?
使用方法
准备问题访谈脚本
I want to validate this problem hypothesis: [problem statement]
Target customer: [who]
Create a problem interview script with open-ended questions.
分析问题访谈结果
I conducted [X] problem interviews. Here's what I learned: [summary]
Analyze whether the problem is validated.
What should I do next?
设计问题访谈实验
Help me design a problem interview experiment to test:
Hypothesis: [problem hypothesis]
Target: [customer segment]
Sample size and success criteria needed.
说明
步骤 1:定义你的问题假设
## Problem Hypothesis Template
### The Problem Statement
"I believe [customer segment] has a problem with [problem area]
because [reason/observation]."
### Assumptions to Validate
| # | Assumption | Confidence | Evidence |
|---|------------|------------|----------|
| 1 | The problem exists | Low/Med/High | None yet |
| 2 | The problem is frequent (happens often) | Low/Med/High | None yet |
| 3 | The problem is severe (causes real pain) | Low/Med/High | None yet |
| 4 | People are actively seeking solutions | Low/Med/High | None yet |
| 5 | Current solutions are inadequate | Low/Med/High | None yet |
### What Would Invalidate This?
- If fewer than [X%] mention this problem unprompted
- If the problem happens less than [frequency]
- If severity rating is below [threshold]
- If people aren't spending time/money to solve it
步骤 2:规划问题访谈
## Problem Interview Framework
### Interview Goals
1. Understand the CONTEXT where the problem occurs
2. Measure the SEVERITY of the problem
3. Discover EXISTING SOLUTIONS they use
4. Identify FREQUENCY of the problem
5. Find the COST (time, money, emotion) of the problem
### Interview Structure (30 minutes)
**Part 1: Context Setting (5 min)**
- "Tell me about your role and what you're responsible for..."
- "Walk me through a typical day/week..."
- Goal: Understand their world before diving into problems
**Part 2: Problem Exploration (15 min)**
- "What are the biggest challenges you face with [area]?"
- "Tell me about the last time [problem] happened..."
- "What was the hardest part about that?"
- "How often does this happen?"
- Goal: Deep dive into problem, frequency, severity
**Part 3: Current Solutions (7 min)**
- "How do you handle this today?"
- "What have you tried in the past?"
- "What works? What doesn't?"
- "What do you wish existed?"
- Goal: Understand competitive landscape from customer view
**Part 4: Impact & Close (3 min)**
- "How much time/money does this cost you?"
- "If this problem disappeared, what would change?"
- "Who else deals with this that I should talk to?"
- Goal: Quantify impact, get referrals
步骤 3:提出不带诱导性的问题
## Problem Interview Questions
### Opening Questions (Broad to Specific)
"I'm researching how [people like you] handle [problem area].
I'm not selling anything—just trying to understand the reality."
### Problem Discovery Questions
**Existence:**
- "What's the most frustrating part of [area]?"
- "Walk me through the last time you dealt with [problem]..."
- "What keeps you up at night about [area]?"
**Frequency:**
- "How often does [problem] happen?"
- "When was the last time? The time before that?"
- "Is this daily? Weekly? Monthly?"
**Severity:**
- "On a scale of 1-10, how painful is this?"
- "What happens if you don't solve this?"
- "How does this affect your [work/life/business]?"
**Emotional Impact:**
- "How does it feel when this happens?"
- "What emotions come up when you deal with this?"
- "What would it mean to you to solve this?"
### Existing Solution Questions
**Current Behavior:**
- "How do you handle this today?"
- "What tools/processes do you use?"
- "Walk me through your current workflow..."
**Past Attempts:**
- "What have you tried before?"
- "What worked? What didn't?"
- "Why did you stop using [previous solution]?"
**Ideal State:**
- "If you had a magic wand, what would you change?"
- "What would the perfect solution look like?"
- "What would need to be true for this to be solved?"
### Impact Questions
**Quantification:**
- "How much time do you spend on this per week?"
- "How much does this cost you?" (direct and indirect)
- "What's the opportunity cost of not solving this?"
**Urgency:**
- "Is solving this a priority? Why/why not?"
- "What would make it urgent?"
- "Have you looked for solutions recently?"
### DON'T Ask These
❌ "Would you use a product that...?" (leading)
❌ "Don't you think [solution] would help?" (leading)
❌ "Is [feature] important to you?" (leading)
❌ "Would you pay for...?" (hypothetical, save for later)
步骤 4:衡量问题严重程度
## Problem Severity Assessment
### During Interview - Probe for:
**Time Cost:**
- "How much time do you spend on this?"
- Convert to $ (hourly rate × time)
**Money Cost:**
- Direct costs (tools, services, fixes)
- Indirect costs (opportunity cost, delays)
**Emotional Cost:**
- Frustration level
- Impact on job satisfaction
- Stress and worry
### Severity Scoring Framework
| Signal | Low (1-3) | Medium (4-6) | High (7-10) |
|--------|-----------|--------------|-------------|
| Frequency | Rarely | Monthly/weekly | Daily |
| Time spent | Minutes | Hours | Days |
| Money impact | <$100/mo | $100-1000/mo | >$1000/mo |
| Emotional | Annoyed | Frustrated | Distressed |
| Action taken | None | Some searching | Actively seeking |
| Budget allocated | None | Considering | Has budget |
### Severity Evidence
**Strong validation signals:**
- They brought up the problem before you asked
- They got emotional when describing it
- They've already spent money trying to solve it
- They can quantify the impact precisely
- They asked if you have a solution
**Weak validation signals:**
- Only mentioned when directly asked
- Vague about impact ("it's kind of annoying")
- Never tried to solve it
- Can't quantify the cost
- No urgency in their voice
步骤 5:分析并做出决定
## Problem Interview Analysis
### Interview Summary Template
**Interview #[X]**
**Date:** _______________
**Participant:** [Role, Company type]
| Question Area | Response Summary | Severity (1-10) |
|---------------|------------------|-----------------|
| Problem existence | | |
| Frequency | | |
| Current solution | | |
| Impact/cost | | |
| Urgency | | |
**Key Quotes:**
- "[Verbatim quote about the problem]"
- "[Quote about severity/impact]"
**Observed Emotions:**
- [ ] Frustrated [ ] Stressed [ ] Resigned [ ] Energized when discussing
- [ ] No emotional reaction (weak signal)
---
### Aggregate Analysis (After 10+ Interviews)
| Metric | Target | Actual | Validated? |
|--------|--------|--------|------------|
| Mentioned problem unprompted | >50% | | |
| Average severity score | >7/10 | | |
| Currently spending to solve | >30% | | |
| Would prioritize solving | >50% | | |
| Can quantify impact | >60% | | |
### Decision Framework
**VALIDATED - Proceed to Solution Interviews if:**
- [ ] 7+ of 10 mentioned problem unprompted
- [ ] Average severity > 7/10
- [ ] Multiple people already spending on solutions
- [ ] Clear patterns in problem description
- [ ] Consistent emotional response
**NOT VALIDATED - Pivot if:**
- [ ] Fewer than 5 of 10 recognize the problem
- [ ] Severity consistently < 5/10
- [ ] No one is actively trying to solve it
- [ ] Wide variance in problem descriptions
- [ ] "Nice to have" language dominates
**NEEDS MORE RESEARCH if:**
- [ ] Mixed signals (some strong, some weak)
- [ ] Different sub-segments show different patterns
- [ ] Problem exists but may not be the ONE to solve
示例
示例 1:B2B 问题访谈
输入:
“我想验证营销经理是否难以跨渠道追踪营销活动的投资回报率。请创建一份问题访谈脚本。”
输出:
问题访谈脚本:营销活动投资回报率
**假设:**中型 B2B 公司中的营销经理难以追踪和报告多个渠道的营销活动投资回报率。
开场(2 分钟)
“感谢你抽时间交流。我正在研究营销团队如何衡量绩效。我不是来推销的,只是想了解实际情况。可以问你一些关于如何追踪营销成果的问题吗?”
了解背景(3 分钟)
- “说说你的职位吧。你负责什么?”
- “你们公司如何衡量营销成效?”
- “你的营销工具栈里有哪些工具?”
探索问题(12 分钟)
问题是否存在: 4. “衡量营销绩效时,最棘手的部分是什么?” 5. “请带我回顾一下上次 CEO 询问营销投资回报率时发生的情况……” 6. “你目前如何回答‘哪些做法有效,哪些无效?’这个问题?”
出现频率: 7. “你多久需要报告一次营销绩效?” 8. “你每周/每月会在这件事上花多少时间?”
严重程度(深入追问): 9. “当你无法回答投资回报率相关问题时,会发生什么?” 10. “说说曾经因缺乏可见性而导致问题的一次经历……” 11. “按 1 到 10 分打分,这部分工作让你有多沮丧?”
当前解决方案(8 分钟)
- “你们现在是如何处理这个问题的?请带我了解一下你们的流程……”
- “你们使用什么工具来生成报告?”
- “你们目前的方法有哪些优点?”
- “有哪些地方让你觉得沮丧?”
- “你们尝试过其他解决方案吗?结果如何?”
影响与收尾(5 分钟)
- “如果你能清楚了解 ROI,会有什么改变?”
- “现在解决这个问题对你来说是优先事项吗?为什么?”
- “需要满足什么条件,这件事才会变得紧迫?”
- “你团队里还有谁也在处理这个问题,是我应该找来聊聊的?”
给自己的备注
- 留意:情绪化的措辞、具体示例、量化的影响
- 危险信号:回答含糊、“还行”、没有紧迫感
- 强烈信号:他们曾尝试解决问题,也能量化问题造成的成本
示例 2:问题访谈分析
输入:
“我围绕自由职业者的财务规划做了 12 次问题访谈。以下是我的总结。这个问题得到验证了吗?”
提供的总结:
- 9/12 的人表示,他们“应该”更擅长理财
- 6/12 的人提到了报税季的压力
- 4/12 的人目前使用某种工具
- 大多数人表示,他们使用电子表格,或者什么都不用
- 平均严重程度:5.5/10
- 只有 2 人正在积极寻找解决方案
输出:
问题访谈分析
评估表
| 指标 | 目标 | 实际情况 | 状态 |
|---|---|---|---|
| 对问题的认知 | >70% | 75%(9/12) | ✅ |
| 平均严重程度 | >7/10 | 5.5/10 | ❌ |
| 积极寻找解决方案 | >30% | 17%(2/12) | ❌ |
| 目前为解决方案付费 | >30% | 33%(4/12) | ⚠️ |
诊断:部分得到验证
已验证的内容:
- 人们意识到自己存在问题(9/12)
- 存在一个具体的痛点(报税季)
- 工具采用率低,说明存在机会
尚未验证的内容:
- 严重程度太低(5.5,低于 7+ 的目标)
- 积极寻找解决方案的人很少(2/12)
- 他们说的是“应该”,而不是“必须”(这是义务感,而非紧迫感)
关键洞察
这是一个已知的问题,却不是切身感受到的问题。人们知道自己“应该”更擅长理财,但这个问题还不够令人痛苦,不足以促使他们采取行动。这是典型的“维生素”问题(有了更好)与“止痛药”问题(必不可少)之间的区别。
建议
选项 1:找到最迫切的痛点
- 深入了解提到报税季压力的 6 个人
- 是否有某个具体的触发时刻,会让事情变得紧迫?
- “带我了解一下去年 4 月 14 日发生了什么……”
- 问题也许不是“财务规划”,而是“报税季恐慌”
选项 2:寻找不同的细分群体
- 积极寻找解决方案的 2 个人是谁?他们有什么不同?
- 高收入的自由职业者(他们面临的风险更大)?
- 刚刚遇到意外税务问题的自由职业者?
- 找到严重程度确实达到 8+ 的细分群体
选项 3:调整问题方向
- 他们还提到了哪些令人痛苦的事情?
- 问题也许不在于财务规划
- “收入不稳定带来的压力”或“发票逾期”也许更为迫切
后续步骤
- 访谈另外 5 位刚经历过报税季的人
- 访谈积极寻找解决方案的 2 个人,了解原因
- 提问:“今年你经历过的最让你焦虑的财务时刻是什么?”
在明确的细分群体中,问题严重程度超过 7/10 之前,不要继续进行解决方案访谈。
示例 3:深入了解问题的严重程度
输入:
“在问题访谈中,人们会说‘嗯,这挺烦人的’,但我不确定问题是否严重到值得解决。我该如何深入追问?”
输出:
探询严重程度的技巧
“5 个为什么”方法
不断追问“为什么”,直到找到真正的痛点:
表面:“是啊,记账真的很烦。”
追问 1:“为什么觉得烦?” →“因为我得从各处收集收据。”
追问 2:“为什么这会造成问题?” →“因为报税时我会漏掉抵扣项。”
追问 3:“漏掉抵扣项为什么重要?” →“我去年可能多缴了 3,000 美元的税。”
追问 4:“这对你有什么影响?” →“这些钱本来可以拿去投资,也可以用来度假。”
追问 5:“如果能拿回这 3,000 美元,对你意味着什么?” →“那可够去欧洲旅行了。每次报税时我都会想到这件事。”
**现在我们得到了:**具体痛点(3,000 美元)、情感分量(一直惦记着)、切实影响(错失度假)。
“最坏情况”技巧
“如果这个问题一直得不到解决,最糟糕的情况会是什么?”
表面:“我的工具生成的报告不太好。”
追问:“如果这种情况持续下去,最糟糕的情况会是什么?” →“我想,CEO 会继续问我答不上来的问题。”
追问:“然后会怎样?” →“最后他们会质疑营销投入是否值得。”
追问:“接下来呢?” →“预算被削减。或者销售额下滑时,我会背锅,而我们又无法证明营销有效。”
**现在我们得到了:**对工作保障的担忧、保护预算的需求、问责压力。
“金钱”技巧
始终尝试量化:
“你提到这很耗时。能量化一下吗?” →“每周大概 5 小时。”
“如果你的综合成本是每小时 80 美元,那么光这项任务每年就要花 20,000 美元。你觉得准确吗?” →“哇,我从没这么想过。是啊……这可不少。”
“情绪”技巧
留意并追问情绪:
对方:“这让人很沮丧。”
你:“具体是怎么沮丧?带我回想一下,当时是什么感受。” →“我压力很大,手忙脚乱。老板还在等结果。晚上 10 点我还在翻电子表格,因为白天拿不到所需的数据。”
**现在我们得到了:**压力、时间紧迫感、对工作与生活的影响。
严重程度验证信号
| 信号 | 含义 |
|---|---|
| 不用提示就主动量化 | 他们已经为此思考了很多 |
| 他们情绪激动 | 这件事确实让他们很困扰 |
| 他们尝试过多种解决方案 | 他们在积极解决问题 |
| 他们询问你是否有解决方案 | 他们准备购买 |
| 他们愿意为抢先体验付费 | 已得到验证 |
| 他们把你推荐给其他人 | 社群痛点 |
清单与模板
问题访谈准备清单
## Before the Interview
□ Problem hypothesis written down
□ Assumptions to validate listed
□ Interview questions prepared
□ Note-taking system ready
□ Recording permission (if recording)
□ 30 minutes blocked
## During the Interview
□ Don't mention your solution
□ Ask open-ended questions
□ Let them do 70%+ of talking
□ Probe on severity (5 whys)
□ Get specific examples, not generalities
□ Listen for emotional language
□ Quantify impact (time, money)
□ Ask for referrals
## After the Interview
□ Write summary within 1 hour
□ Extract key quotes
□ Score severity (1-10)
□ Note signals (strong/weak)
□ Update hypothesis based on learnings
问题访谈跟踪表
| # | Date | Participant | Problem Confirmed? | Severity | Active Seeking? | Key Quote |
|---|------|-------------|-------------------|----------|-----------------|-----------|
| 1 | | | Y/N | 1-10 | Y/N | |
| 2 | | | Y/N | 1-10 | Y/N | |
**Running Analysis:**
- Problem confirmation rate: ___%
- Average severity: __/10
- Active seeking rate: ___%
- Validation status: Validated / Not Yet / Needs Pivot
技能边界
此技能擅长的方面
- 设计音频制作工作流
- 提供技术指导
- 创建质量检查清单
- 提出创意方法
此技能无法做到的方面
- 取代音频工程专业知识
- 做出主观的创意决策
- 直接访问或编辑音频文件
- 保证商业成功
参考资料
- Alvarez, Cindy.《精益客户开发》(2014)——问题访谈方法
- Fitzpatrick, Rob.《妈妈测试》(2013)——提问技巧
- Blank, Steve.《顿悟之路的四个步骤》(2005)——客户开发
- Torres, Teresa.《持续发现习惯》(2021)——持续发现
相关技能
技能元数据
- 模式:cyborg
name: problem-interview
category: validation
subcategory: customer-research
version: 1.0
author: MKTG Skills
source_expert: Cindy Alvarez
source_work: Lean Customer Development
difficulty: beginner
estimated_value: $1,500 customer research training
tags: [validation, interviews, customer-discovery, problems, startups, YC]
created: 2026-01-25
updated: 2026-01-25