customer-interviews

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Mastering Customer Interviews

精通客户访谈

Uncover deep user pain and behavioral triggers to build products people actually need.

Help the user with mastering customer interviews using insights from 11 guests and posts across Lenny's Podcast and Newsletter.

挖掘用户深层痛点与行为触发因素，打造真正符合用户需求的产品。

借助Lenny播客和新闻通讯中11位嘉宾的分享及相关文章，帮助用户掌握客户访谈技巧。

How to Help

如何提供帮助

Define objectives - Identify the specific problem area or user segment you want to explore before recruiting participants.
Draft the guide - Create open-ended questions that focus on past behaviors and struggling moments rather than hypothetical opinions.
Synthesize findings - Analyze interview notes to distinguish between polite encouragement and genuine user pull.
Validate pain - Evaluate whether the identified problems are painful enough to warrant a new solution or behavioral change.

明确目标 - 在招募受访者前，确定你想要探索的具体问题领域或用户群体。
草拟访谈指南 - 设计开放式问题，聚焦用户过往行为和遇到的困境，而非假设性观点。
整合调研结果 - 分析访谈记录，区分礼貌性的认可与用户真实的需求倾向。
验证痛点 - 评估已发现的问题是否严重到值得开发新解决方案或推动用户行为改变。

Core Principles

核心原则

Focus on causal triggers

聚焦触发因素

Bob Moesta: "And so the real heart of the method of Jobs to Be Done is understanding the causation of what pushes people to say, 'Today's the day I got to do something different.'"

Interviews should uncover the specific events and context that led to a change in behavior. Understanding the struggling moment makes seemingly irrational user choices appear rational.

Bob Moesta: "Jobs to Be Done方法的核心在于理解是什么促使人们下定决心‘今天我必须做出改变’的原因。"

访谈应揭示导致用户行为改变的具体事件和背景。理解用户的困境时刻，能让看似不合理的用户选择变得合乎逻辑。

Observe unarticulated pain

挖掘未被表达的痛点

Jag Duggal: "You make sure that you focus on customer discovery before you start building. You make sure that that discovery is focused not simply on asking the customer, but on innovating on their behalf."

Effective research goes beyond listening to explicit requests by observing users in their natural environment. This reveals friction points that users may not be able to describe.

Jag Duggal: "确保在开始开发前先聚焦客户探索，并且这种探索不只是倾听客户的诉求，还要代表他们进行创新。"

有效的调研不应局限于倾听用户明确提出的需求，还要观察用户在真实场景中的行为，这能发现用户自身无法描述的摩擦点。

Actively seek disproof

主动寻求反证

Shaun Clowes: "Avoid availability or confirmation bias. Most of the time people go talk to the people they always talk to and they learn nothing particularly new. They don't synthesize the results that they got from that conversation. They don't seek out the counterfactual, they don't seek out the proof that they're wrong."

To avoid confirmation bias, you must intentionally seek out data points that disprove your current assumptions. Learning is maximized when you find counterfactual perspectives.

Shaun Clowes: "避免可得性偏差或确认偏差。大多数时候，人们只会和熟悉的人交流，无法获得新的认知。他们不会整合对话中的结果，也不会寻找反例，不会去证明自己是错的。"

为避免确认偏差，你必须主动寻找能推翻当前假设的数据点。当你找到相反的观点时，学习效果是最大化的。

Prioritize direct observation

优先直接观察

From "How to develop product sense": "Don’t just read reports from researchers on your team; instead attend user research sessions to get firsthand exposure to user experiences and reactions. What’s important is to pay attention to micro details and ask yourself why people react to your product the way they do."

Directly observing user behavior provides a firsthand understanding of emotional and functional needs. Research reports often overlook the nuance found in live reactions.

From "How to develop product sense": "不要只阅读团队研究员的报告；相反，要亲自参与用户调研环节，直接接触用户的体验和反应。重要的是关注微小细节，并思考用户为何会对产品做出这样的反应。"

直接观察用户行为能让你第一手了解用户的情感和功能需求。调研报告往往会忽略实时反应中的细微差别。

Avoid the sales pitch

避免推销式访谈

From "Startup to exit: Lessons from a first-time founder": "However, we realized our first several “interviews” were actually sales pitches (e.g. “here’s this cool new thing, what do you think?”). Far too biased to get any real signal."

Running discovery calls as sales pitches prevents honest signals. Use an unbiased script that avoids mentioning your specific solution to see if the customer brings up the problem organically.

From "Startup to exit: Lessons from a first-time founder": "然而，我们意识到最初的几次‘访谈’实际上是推销（比如：‘这是我们的新产品，你觉得怎么样？’）。这种方式带有太强的偏见，无法获得真实的反馈信号。"

将探索性对话变成推销会阻碍获得真实反馈。使用中立的访谈脚本，避免提及你的具体解决方案，看用户是否会主动提出相关问题。

Listen for signs of pull

倾听需求倾向信号

From "What to do if your product isn’t taking off": "When talking to people, look for two things: pain and pull. Pain tells you there’s an opportunity to solve a problem. Pull tells you that you’re actually solving the problem."

Ignore polite encouragement and look for signs of intense pain. Real pull is evidenced by people paying money or continuing to use a bad prototype despite its flaws.

From "What to do if your product isn’t taking off": "与用户交流时，要关注两点：痛点和需求倾向。痛点告诉你存在解决问题的机会，需求倾向则表明你确实在解决用户的问题。"

忽略礼貌性的认可，寻找强烈痛点的信号。真正的需求倾向体现在用户愿意付费，或者即使原型存在缺陷仍持续使用。

Templates & Frameworks

模板与框架

Jobs-to-be-Done Interrogation Technique (Robby Stein) - Clayton Christensen's interview/interrogation method for understanding why users hire a product, distinguishing utility jobs from emotional jobs
Nielsen Number for Research Right-Sizing (Shaun Clowes) - The principle that 7-14 user interviews is the sweet spot—fewer than 7 means not enough data, more than 14 means diminishing returns.
Four Signals of Pain and Pull (What to do if your product isn’t taking off) - Four concrete indicators that tell you whether your product is solving a real problem, used during customer discovery conversations
Gusto's Emotional Reaction Test for Customer Interviews (How to validate your B2B startup idea) - A framework for evaluating whether customer interview feedback indicates genuine demand, based on the intensity of emotional response
Story-Based Interview Technique (Teresa Torres) - An interviewing method where you collect specific behavioral stories from customers by asking about a recent concrete experience and then following the timeline
Automated Customer Interview Recruiting System (Teresa Torres) - A system for automating weekly customer interview scheduling so product teams can maintain a continuous interviewing cadence without manual recruiting effort
Seven Signals to Look for in User Conversations (Prioritizing at startups) - What to listen for when talking to early users and potential users to generate product ideas

See

references/artifacts.md

for the full list with details.

Jobs-to-be-Done 访谈问询技巧 (Robby Stein) - Clayton Christensen提出的访谈/问询方法，用于理解用户为何选择某款产品，区分功能性需求与情感性需求
Nielsen 调研规模优化原则 (Shaun Clowes) - 7-14次用户访谈是黄金区间——少于7次意味着数据不足，多于14次则新见解的收益会递减。
痛点与需求倾向的四大信号 (What to do if your product isn’t taking off) - 用于客户探索对话中的四个具体指标，判断你的产品是否解决了真实问题
Gusto 客户访谈情感反应测试 (How to validate your B2B startup idea) - 基于用户情感反应强度，评估客户访谈反馈是否表明真实需求的框架
基于故事的访谈技巧 (Teresa Torres) - 一种访谈方法，通过询问用户近期的具体经历并按时间线跟进，收集用户的具体行为故事
自动化客户访谈招募系统 (Teresa Torres) - 用于自动化每周客户访谈日程安排的系统，让产品团队无需手动招募就能持续开展访谈
用户对话中需关注的七大信号 (Prioritizing at startups) - 与早期用户和潜在用户交流时，需留意哪些信号以生成产品创意

See

references/artifacts.md