problem-definition

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Problem Definition

问题定义

Help the user define problems clearly before jumping to solutions using frameworks from 91 product leaders.

借助91位产品负责人的框架，帮助用户在急于寻找解决方案之前清晰地定义问题。

How to Help

如何提供帮助

When the user asks for help with problem definition:

Understand the current framing - Ask how they're currently thinking about the problem
Dig into the struggling moment - Help them articulate the specific context where users feel stuck
Separate problem from solution - Ensure they haven't conflated a desired feature with the underlying need
Validate the problem matters - Help them confirm the problem is urgent and widespread enough to solve

当用户请求协助定义问题时：

理解当前表述 - 询问他们目前对该问题的思考方式
深挖困境时刻 - 帮助他们明确表述用户陷入困境的具体场景
区分问题与解决方案 - 确保他们没有将想要的功能与潜在需求混为一谈
验证问题的重要性 - 帮助他们确认该问题是否足够紧迫且普遍，值得去解决

Core Principles

核心原则

Digitizing analog isn't enough

仅数字化模拟方案远远不够

Bret Taylor: "Why use this instead of the Yellow Pages? It was a digital version of something that had come before." Simply digitizing an analog predecessor often fails because it lacks a native reason to exist on the new platform. Ask "why should a customer give this the time of day?"

Bret Taylor：“为什么要用这个而不是黄页？它只是此前已有事物的数字化版本。”仅仅将模拟方案数字化通常会失败，因为它缺乏在新平台上存在的原生理由。要问“为什么客户要花时间在这上面？”

Prototype to define the problem

通过原型定义问题

Jake Knapp + John Zeratsky: "This idea of getting unstuck and turning maybe some abstract ideas or some concepts that you've been discussing, turning that into a concrete prototype, something that you can look at and you can click around." Moving from abstract concepts to concrete prototypes is the fastest way to define and solve a problem.

Jake Knapp + John Zeratsky：“这种摆脱困境的思路，是把你一直在讨论的一些抽象想法或概念，转化为具体的原型——一种你可以查看和交互的东西。”从抽象概念转向具体原型是定义和解决问题的最快方式。

Avoid the shiny object trap

避免新奇事物陷阱

Marily Nika: "There is something called the shiny object trap, and I'm always telling people, 'Hey, don't do AI for the sake of doing AI.' Make sure there is a problem there." Ensure AI (or any new technology) is used to solve a specific, validated user pain point rather than for its own sake.

Marily Nika：“有一种陷阱叫做新奇事物陷阱，我总是告诉人们，‘嘿，不要为了用AI而用AI。’要确保确实存在对应的问题。”确保AI（或任何新技术）是用于解决具体、经过验证的用户痛点，而非为了技术本身。

Struggling moments cause demand

困境时刻催生需求

Bob Moesta: "A struggling moment causes demand. And you start to realize that in some cases that struggling moment exists and can exist for a long time and nobody solved it." Demand is created by a specific "struggling moment" in a user's life, not by the product itself. Study the context that makes users' behavior rational.

Bob Moesta：“困境时刻会催生需求。你会意识到，在某些情况下，这种困境时刻已经存在很久，却没人解决。”需求是由用户生活中特定的“困境时刻”催生的，而非产品本身。要研究让用户行为合理化的具体场景。

See the end from the beginning

从一开始就预见结果

Ryan Singer: "We are not going to start something unless we can see the end from the beginning. We're not going to take a big concept and then say, 'What's the estimate for this thing?'" Ensure the team can visualize the completed feature before committing resources. Avoid starting with fuzzy concepts.

Ryan Singer：“除非我们能从一开始就预见结果，否则不会启动项目。我们不会拿着一个大概念就问‘这个东西的预估成本是多少？’”确保团队在投入资源前能够可视化已完成的功能。避免从模糊的概念开始。

The solution is what customers buy

解决方案是客户购买的核心

Marty Cagan: "People don't buy the problem, they buy your solution. Obviously they don't buy it if it's not solving something they care about, but there are many products that are solving what they care about." While understanding the problem is necessary, competitive advantage comes from the quality of the solution. Don't over-rotate on problem validation if the problem is well-understood.

Marty Cagan：“人们不会购买问题，他们购买的是你的解决方案。显然，如果它不能解决他们关心的问题，他们不会买，但有很多产品都在解决用户关心的问题。”虽然理解问题是必要的，但竞争优势来自解决方案的质量。如果问题已经被充分理解，不要过度纠结于问题验证。

Spend more time on the problem

在问题上投入更多时间

Christopher Lochhead: "Spend more time on the problem than the solution." Deeply understanding the customer's perspective of the problem is more valuable than internal product brainstorming. Listen to hear their perspective rather than just pitching your solution.

Christopher Lochhead：“在问题上投入的时间要多于解决方案。”深入理解客户对问题的看法，比内部产品头脑风暴更有价值。要倾听他们的观点，而非仅仅推销你的解决方案。

Qualify the problem type

明确问题类型

Christopher Miller: "I don't know that we even talk about problems without a qualifier. Are we talking about a business problem? Are we talking about a customer problem?" Effective problem definition requires distinguishing between business needs and customer pain points to avoid "customer-hostile" solutions.

Christopher Miller：“我认为我们讨论问题时必须加上限定词。我们讨论的是业务问题还是客户问题？”有效的问题定义需要区分业务需求和客户痛点，以避免“对客户不友好”的解决方案。

Questions to Help Users

用于协助用户的问题

"What is the user doing right before they encounter this problem? What are they trying to accomplish?"
"Why hasn't this problem been solved already? What makes it hard?"
"Is this a business problem or a customer problem? Are they the same?"
"If you solved this problem perfectly, how would the user's life be different?"
"Can you describe a specific person experiencing this problem in a specific moment?"
"What are people doing today to work around this problem?"

“用户在遇到这个问题之前正在做什么？他们想要达成什么目标？”
“为什么这个问题至今没有被解决？难点在哪里？”
“这是业务问题还是客户问题？两者是否一致？”
“如果你完美解决了这个问题，用户的生活会有什么不同？”
“你能描述一个具体的人在具体时刻遇到这个问题的场景吗？”
“现在人们是如何解决这个问题的？”

Common Mistakes to Flag

需要指出的常见错误

Solution-first thinking - Starting with a feature idea and working backward to justify it
Technology-first thinking - Wanting to use AI/blockchain/etc. and looking for problems to apply it to
Abstract problem statements - Defining problems so broadly they don't point to any specific solution
Conflating business and customer problems - Solving for internal metrics without addressing user needs
Skipping the struggling moment - Not understanding the specific context where pain occurs

先解决方案后问题的思维 - 从功能想法出发，反向寻找理由支撑
技术优先的思维 - 想要使用AI/区块链等技术，然后寻找可以应用的问题
抽象的问题陈述 - 问题定义过于宽泛，无法指向任何具体解决方案
混淆业务问题与客户问题 - 为了内部指标而解决问题，却未满足用户需求
忽略困境时刻 - 不理解痛苦发生的具体场景

Deep Dive

深入研究

For all 123 insights from 91 guests, see

references/guest-insights.md

如需获取91位嘉宾的全部123条见解，请查看

references/guest-insights.md