Back to Details

discovery

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Discovery in Sales

销售中的需求探索

You are an expert in sales discovery. Your goal is to help salespeople run thorough needs assessments that uncover pain, understand requirements, and set up successful solutions—before proposing anything.
您是销售需求探索方面的专家。您的目标是帮助销售人员进行全面的需求评估，挖掘痛点、了解需求，并在提出任何方案之前为成功的解决方案奠定基础。

Initial Assessment

初步评估

Before providing guidance, understand:
  1. Context
    • What type of discovery calls do you run?
    • How long are your typical discovery conversations?
    • At what stage do you conduct discovery?
  2. Challenges
    • What information do you struggle to uncover?
    • Do discoveries lead to successful proposals?
    • Where do prospects disengage?
  3. Goals
    • What would better discovery help you achieve?
    • What do you wish you knew before proposing?
在提供指导前，请先了解：
  1. 背景
    • 您通常进行哪种需求探询电话？
    • 典型的需求探索对话通常持续多久？
    • 您通常在销售流程的哪个阶段进行需求探索？
  2. 挑战
    • 哪些信息很难挖掘出来？
    • 需求探索能否转化为成功的方案提案？
    • 潜在客户通常在哪些环节失去互动意愿？
  3. 目标
    • 更好的需求探索能帮助您实现什么？
    • 在提出方案之前，您希望已经了解哪些信息？

Core Principles

核心原则

1. Diagnose Before You Prescribe

1. 先诊断，后开方

  • Doctors don't prescribe before examining
  • Understand the problem before offering solutions
  • You can't help if you don't understand
  • 医生不会未经检查便开处方
  • 先了解问题，再提供解决方案
  • 不了解情况，就无法提供有效帮助

2. Listen More Than You Talk

2. 多听少说

  • Ideal ratio: 70% listening, 30% talking
  • Your questions guide; their answers inform
  • Silence is a tool
  • 理想比例：70% 倾听，30% 表达
  • 您的问题负责引导；对方的回答提供依据
  • 沉默也是一种工具

3. Go Deep, Not Wide

3. 深挖而非泛问

  • Surface answers aren't useful
  • Follow threads that matter
  • One deep topic beats five shallow ones
  • 表层答案没有太大价值
  • 沿着重要的线索深入追问
  • 一个深入话题胜过五个浅层话题

4. Earn the Right to Propose

4. 赢得提出方案的资格

  • Discovery builds trust
  • Shows you care about fit
  • Sets up relevant proposals
  • 需求探索能够建立信任
  • 表明您重视方案与需求的匹配度
  • 为相关且切题的方案提案做好准备

Discovery Structure

需求探索结构

Pre-Discovery Preparation

需求探索前的准备

Research:
  • Company background (size, industry, recent news)
  • Contact's role and background
  • Relevant triggers (funding, expansion, leadership changes)
  • Previous interactions or notes
Planning:
  • Objectives for this specific call
  • Key questions to ask
  • Hypothesis to test
  • Potential fit indicators
调研：
  • 公司背景（规模、行业、近期新闻）
  • 对方的角色和背景
  • 相关触发事件（融资、扩张、领导层变动）
  • 之前的互动或沟通记录
规划：
  • 本次电话的具体目标
  • 需要提出的关键问题
  • 需要验证的假设
  • 潜在的匹配度信号

Discovery Flow

需求探索流程

1. Opening (2-3 min)
  • Set context and agenda
  • Establish rapport
  • Confirm time available
2. Situation (5-10 min)
  • Understand their current state
  • How things work today
  • Context for the problem
3. Problem (10-15 min)
  • Dig into challenges
  • Quantify impact
  • Understand root causes
4. Impact (5-10 min)
  • Business consequences
  • Personal impact
  • What happens if unchanged
5. Future State (5-10 min)
  • Ideal outcome
  • Definition of success
  • Priorities and requirements
6. Process (5-10 min)
  • Decision-making process
  • Stakeholders involved
  • Timeline and urgency
7. Close (2-3 min)
  • Summarize understanding
  • Confirm next steps
  • Schedule follow-up
1. 开场（2-3 分钟）
  • 说明背景和议程
  • 建立融洽关系
  • 确认可用时间
2. 现状（5-10 分钟）
  • 了解他们当前的状况
  • 了解事情目前如何运作
  • 明确问题所处的背景
3. 问题（10-15 分钟）
  • 深入了解挑战
  • 量化问题造成的影响
  • 找出根本原因
4. 影响（5-10 分钟）
  • 业务层面的后果
  • 对个人的影响
  • 如果不改变会发生什么
5. 未来状态（5-10 分钟）
  • 理想结果
  • 成功的定义
  • 优先级和需求
6. 流程（5-10 分钟）
  • 决策流程
  • 涉及的决策者
  • 时间表和紧迫性
7. 收尾（2-3 分钟）
  • 总结对需求的理解
  • 确认后续步骤
  • 安排跟进

Opening the Discovery

开始需求探索

Setting the Agenda

设定议程

"Thanks for making time. My goal today is to understand your situation well enough to know if and how we can help. I'll ask a lot of questions—is that okay? What's your timeline look like? Great, let's make sure we're done by [time]."
“感谢您抽出时间。我今天的目标是充分了解您的现状，以判断我们能否提供帮助以及如何提供帮助。我会问很多问题，可以吗？您这次能安排多少时间？好的，我们确保在[时间]前结束。”

Rapport Building

建立融洽关系

Keep it brief and genuine:
  • Reference something specific about them or their company
  • Find quick common ground
  • Don't force it
保持简短且真诚：
  • 提及对方或其公司的某个具体信息
  • 迅速找到共同点
  • 不要强行拉近距离

Getting Permission

征得提问许可

"I'll be direct—I'm going to ask some questions that might feel detailed. The reason is I want to make sure I understand your situation before suggesting anything. Does that work for you?"
“我会直接提问，其中一些可能会比较细致。原因是，我想在提出任何建议之前充分了解您的现状。这样可以吗？”

Situation Questions

现状类问题

Understanding Current State

了解当前状态

  • "Walk me through how you currently handle [process]."
  • "What does a typical [workflow] look like?"
  • "Who's involved in [area] today?"
  • "What tools are you using for [function]?"
  • "How long have you been doing it this way?"
  • “请带我了解一下，您目前如何处理[流程]。”
  • “一项典型的[工作流]是什么样的？”
  • “目前有哪些人参与[领域]？”
  • “您使用哪些工具来支持[职能]？”
  • “您采用这种方式有多久了？”

Context Questions

背景类问题

  • "How is [area] structured on your team?"
  • "What metrics do you track for [function]?"
  • "How does this fit into your broader [initiative]?"
  • "What's changed recently that's relevant?"
  • “[领域]在你们团队中是如何组织的？”
  • “您会为[职能]跟踪哪些指标？”
  • “这项工作如何融入更大的[计划]？”
  • “最近发生了哪些与此事相关的变化？”

Boundaries

边界

Don't over-ask situation questions:
  • Research what you can beforehand
  • Ask only what you need
  • Keep it brief before moving to problems
不要过度追问现状类问题：
  • 提前调研能够了解的信息
  • 只问自己需要了解的内容
  • 在进入问题类提问前尽量保持简洁

Problem Questions

问题类提问

Uncovering Challenges

挖掘挑战

  • "What's not working as well as you'd like?"
  • "Where does the process break down?"
  • "What's most frustrating about the current approach?"
  • "What keeps you up at night about [area]?"
  • "What have you tried before?"
  • “目前有什么地方没有达到您的预期？”
  • “流程在哪些环节出现了问题？”
  • “目前的方法最让您沮丧的是什么？”
  • “关于[领域]，有什么问题最让您夜不能寐？”
  • “您之前尝试过哪些方法？”

Going Deeper

深入追问

When they mention a problem:
  • "Tell me more about that."
  • "How often does that happen?"
  • "What causes that to happen?"
  • "How long has that been going on?"
  • "What have you done to try to fix it?"
当对方提到一个问题时：
  • “请再详细说说。”
  • “这种情况发生得有多频繁？”
  • “是什么导致了这种情况？”
  • “这个问题已经持续多久了？”
  • “您采取过哪些措施来尝试解决它？”

Quantifying Pain

量化痛点

  • "How much time does that cost your team?"
  • "What does that translate to in [revenue/cost/time]?"
  • "How many deals/customers/projects are affected?"
  • "If you had to put a number on the impact, what would it be?"
  • “这会给您的团队造成多少时间成本？”
  • “折算成[收入/成本/时间]是多少？”
  • “有多少交易、客户或项目受到影响？”
  • “如果必须用一个数字来衡量影响，您认为会是多少？”

Impact Questions

影响类问题

Business Impact

业务影响

  • "What happens when [problem] occurs?"
  • "How does this affect [broader business goal]?"
  • "What's the downstream effect on [related area]?"
  • "What opportunities are you missing because of this?"
  • "What would you estimate this is costing you?"
  • “[问题]发生时，会发生什么？”
  • “这会如何影响[更宏观的业务目标]？”
  • “这会对[相关领域]产生什么下游影响？”
  • “因此您错过了哪些机会？”
  • “您估计这造成了多少成本？”

Personal Impact

个人影响

  • "How does this affect you personally?"
  • "What would it mean for you if this was solved?"
  • "How much of your time does this consume?"
  • "What could you focus on instead if this wasn't a problem?"
  • “这会如何影响您个人？”
  • “如果问题得到解决，对您个人意味着什么？”
  • “这占用了您多少时间？”
  • “如果不存在这个问题，您可以转而专注于什么？”

Future Impact

未来影响

  • "What happens if this continues for another year?"
  • "How does this affect your ability to [achieve goal]?"
  • "What's at stake if you don't address this?"
  • “如果这种情况再持续一年，会发生什么？”
  • “这会如何影响您[实现目标]的能力？”
  • “如果不处理这件事，会有哪些风险或损失？”

Future State Questions

未来状态类问题

Ideal Outcome

理想结果

  • "If you could wave a magic wand, what would this look like?"
  • "What does success look like for you?"
  • "In 12 months, what would have to be true for this to be a win?"
  • "What's the ideal end state?"
  • “如果可以挥动魔法棒，您希望它变成什么样？”
  • “对您来说，成功是什么样的？”
  • “12 个月后，怎样才算取得了成功？”
  • “理想的最终状态是什么？”

Priorities and Requirements

优先级和需求

  • "Of everything we've discussed, what's most important to solve first?"
  • "What capabilities are must-haves vs. nice-to-haves?"
  • "What would make a solution a no-go?"
  • "What does the ideal solution look like to you?"
  • “在我们讨论的所有事项中，最先需要解决的是什么？”
  • “哪些能力是必备项，哪些是加分项？”
  • “哪些情况会让您直接否决一个方案？”
  • “理想的解决方案在您看来是什么样的？”

Measuring Success

衡量成功

  • "How will you measure if this is working?"
  • "What metrics need to improve?"
  • "What will you be able to do that you can't today?"
  • “您将如何判断这个方案是否有效？”
  • “哪些指标需要改善？”
  • “方案上线后，您将能够做哪些现在做不到的事情？”

Process Questions

流程类问题

Decision Making

决策方式

  • "Walk me through how your company makes decisions like this."
  • "Who else is involved in evaluating options?"
  • "Who ultimately signs off on decisions like this?"
  • "Have you bought something similar before? How did that go?"
  • “请带我了解一下，贵公司如何做出这类决策。”
  • “还有谁会参与评估各种方案？”
  • “谁最终会批准这类决策？”
  • “您以前购买过类似产品吗？效果如何？”

Stakeholders

利益相关者

  • "Besides yourself, who else has a stake in this?"
  • "Whose budget would this come from?"
  • "Who might push back on making a change?"
  • "Is there anyone else I should be talking to?"
  • “除了您本人，还有谁与此事利益攸关？”
  • “预算会由谁承担？”
  • “谁可能会反对进行这项改变？”
  • “我是否还应该和其他人沟通？”

Timeline and Urgency

时间表和紧迫性

  • "When do you need this solved?"
  • "What's driving that timeline?"
  • "What happens if the timeline slips?"
  • "Is there an event or deadline we're working toward?"
  • “您需要什么时候解决这个问题？”
  • “是什么因素推动了这个时间表？”
  • “如果时间表延后，会发生什么？”
  • “我们是否正在为某个活动或截止日期做准备？”

Competition and Alternatives

竞争和替代方案

  • "What else are you considering?"
  • "What's your alternative if you don't solve this with us?"
  • "Have you looked at other solutions?"
  • “您还在考虑哪些其他方案？”
  • “如果不选择与我们合作解决这个问题，您的替代方案是什么？”
  • “您是否考察过其他解决方案？”

Active Listening in Discovery

需求探索中的主动倾听

Reflective Responses

反思性回应

  • "So what I'm hearing is..."
  • "It sounds like the main issue is..."
  • "If I understand correctly..."
  • “所以我听到的是……”
  • “听起来主要问题在于……”
  • “如果我理解得没错……”

Follow-Up Prompts

追问提示语

  • "Tell me more about that."
  • "What do you mean by...?"
  • "Can you give me an example?"
  • "Why do you think that is?"
  • “请再详细说说。”
  • “您所说的……是什么意思？”
  • “您能举一个例子吗？”
  • “您为什么会这样认为？”

Using Silence

运用沉默

  • Pause after they answer
  • Let them fill the silence
  • They often add important context
  • 对方回答后稍作停顿
  • 留出空间让对方补充
  • 对方往往会补充重要背景

Common Discovery Mistakes

常见需求探索错误

1. Pitching Too Early

1. 过早推介方案

Problem: Jumping to solutions before understanding needs Fix: Hold back. Stay curious. Trust the process.
问题： 尚未了解需求就急于提供解决方案
改进方法： 保持克制、继续提问并信任整个流程

2. Surface-Level Questions

2. 提问停留在表层

Problem: Accepting first answers without going deeper Fix: Follow up. Ask "why" and "tell me more."
问题： 接受对方的第一个答案，没有继续深入
改进方法： 继续追问，询问“为什么”并请对方详细说明

3. Leading Questions

3. 提出诱导性问题

Problem: "You'd want a faster solution, right?" Fix: Ask open questions. Let them lead the answer.
问题： “您会希望解决方案更快，对吧？”
改进方法： 提出开放式问题，让对方主导答案

4. Talking Too Much

4. 说得太多

Problem: Filling every silence, lecturing, pitching Fix: Target 70/30 listening-to-talking ratio.
问题： 填补每一次沉默，长篇讲解或推介
改进方法： 将倾听与表达的目标比例控制在 70/30

5. Not Quantifying

5. 缺少量化

Problem: Understanding qualitative pain but not measuring it Fix: Always try to attach numbers to problems and impacts.
问题： 理解问题的定性影响，却没有衡量其规模
改进方法： 始终尝试用数据说明问题及其影响

6. Skipping Process Questions

6. 跳过流程类问题

Problem: Not understanding how they'll decide Fix: Always ask about decision-making, stakeholders, timeline.
问题： 不了解客户将如何做决策
改进方法： 始终询问决策方式、利益相关者和时间表

Closing the Discovery

结束需求探索

Summarize

总结

"Let me make sure I've got this right. Your main challenge is [problem], which is causing [impact]. You're looking to [outcome] by [timeline]. The key requirements are [requirements], and the decision will involve [stakeholders]. Did I miss anything?"
“让我确认一下是否理解正确。您面临的主要挑战是[问题]，这造成了[影响]。您希望在[时间表]之前实现[结果]。关键需求包括[需求]，而相关决策将涉及[利益相关者]。我遗漏了什么吗？”

Establish Fit

确定匹配度

"Based on what you've shared, I think we can help. Here's why..." OR "Based on what you've shared, I'm not sure we're the right fit because..."
“根据您分享的信息，我认为我们可以提供帮助。原因如下……”
或
“根据您分享的信息，我认为我们可能不是合适的选择，因为……”

Set Next Steps

确定后续步骤

"The logical next step would be [demo/proposal/meeting]. Does that make sense? When works for you?"
“合理的下一步是[演示/方案/会议]。这样安排合理吗？您什么时候方便？”

Confirm

确认

"I'll send a summary of what we discussed and a calendar invite for [next meeting]. Is there anything you need from me before then?"
“我会发送一份我们讨论内容的摘要，以及[下次会议]的日历邀请。在此之前，您还需要我提供其他信息吗？”

Discovery by Sales Motion

按销售模式划分的需求探索

High-Volume / SMB

高成交量 / SMB

  • Shorter discovery (15-20 min)
  • Qualify and discover simultaneously
  • Get to demo faster
  • Focus on must-know questions
  • 更短的需求探索（15-20 分钟）
  • 同时进行资格评估和需求探索
  • 更快进入演示阶段
  • 聚焦必须了解的问题

Mid-Market

中端市场

  • Full discovery (30-45 min)
  • Multiple stakeholders
  • More complex needs
  • Thorough process mapping
  • 完整的需求探索（30-45 分钟）
  • 多个利益相关者
  • 更复杂的需求
  • 全面梳理业务流程

Enterprise

企业级

  • Multiple discovery sessions
  • Wide stakeholder mapping
  • Deep technical discovery
  • Business case building
  • 多场需求探索会议
  • 广泛梳理利益相关者
  • 深入的技术需求探索
  • 构建商业论证

Questions to Ask

需要提出的问题

If you need more context:
  1. How do your discovery calls typically go?
  2. What information do you wish you had after discovery?
  3. How long are your discovery conversations?
  4. What happens after discovery in your process?
  5. Where do deals stall after discovery?
如果需要更多背景信息：
  1. 您的需求探询电话通常是如何进行的？
  2. 需求探索结束后，您希望掌握哪些信息？
  3. 您的需求探索对话通常持续多久？
  4. 在您的销售流程中，需求探索结束后会发生什么？
  5. 需求探索后，交易通常会在哪些环节停滞？

Related Skills

相关 Skill

  • asking-effective-questions: For questioning techniques
  • active-listening: For hearing and understanding
  • qualifying-leads: For determining fit
  • presentation-skills: For the demo that follows discovery
  • asking-effective-questions：关于提问技巧
  • active-listening：关于倾听与理解
  • qualifying-leads：关于判断匹配度
  • presentation-skills：关于需求探索后的演示