idea-validation

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Idea Validation

创意验证

Stop building things people don't want by moving from opinion to evidence-based development.

Help the user with idea validation using insights from 31 guests and posts across Lenny's Podcast and Newsletter.

停止开发用户不需要的产品，从基于主观判断转向基于证据的开发。

借助Lenny播客和通讯中31位嘉宾的分享及文章见解，帮助用户进行创意验证。

How to Help

如何提供帮助

Clarify the Core Hypothesis - Help the user define the specific problem, target audience, and the most 'risky' assumptions using the Founding Hypothesis Scorecard.
Select a Validation Path - Guide the user through choosing between the 'Listening Path', 'Manual Path', or 'Self-Serve Path' based on their proximity to the problem.
Design Low-Fidelity Experiments - Recommend specific 'Wizard of Oz' or 'Fake Door' tests to simulate the solution without building a backend.
Evaluate Signal Quality - Help users distinguish between polite interest and real market pull by looking for financial commitment or high-effort usage.

明确核心假设 - 借助《创始假设评分卡》（Founding Hypothesis Scorecard），帮助用户定义具体问题、目标受众以及最具“风险”的假设。
选择验证路径 - 根据用户与问题的关联程度，引导其选择“倾听路径”（Listening Path）、“手动路径”（Manual Path）或“自助路径”（Self-Serve Path）。
设计低保真实验 - 推荐特定的“奥兹巫师”（Wizard of Oz）或“假门测试”（Fake Door）实验，无需构建后端即可模拟解决方案。
评估信号质量 - 通过观察用户的财务承诺或高投入使用行为，帮助用户区分礼貌性兴趣与真实市场需求。

Core Principles

核心原则

First-Principles De-risking

基于第一性原理降低风险

Bangaly Kaba: "Someone says, 'Hey, you know what? This would be great to build.' And you go pull data to go justify why that would be great to build. Call that identify, justify, execute. First you have to really understand from first principles what is actually going on."

True de-risking starts with understanding the core problem from first principles before looking for data to justify a specific solution.

Bangaly Kaba：“有人说，‘嘿，这个东西开发出来肯定很棒。’然后你就去找数据来证明它确实值得开发。这就是所谓的识别、论证、执行。但首先你必须从第一性原理出发，真正理解实际情况到底是怎样的。”

真正的风险降低始于从第一性原理理解核心问题，而非先找数据来证明某个特定解决方案的合理性。

Maintaining Prototype Momentum

保持原型开发节奏

Grant Lee: "We would have an idea in the morning, come up with some sort of functional prototype, recruit a bunch of people that are legitimately good prospective users, but have zero skin in the game, ship fast so people can start playing with it. In the afternoon, we're already running pretty full scale experiment."

Build functional prototypes within hours of conceiving an idea to maintain speed and identify usability flaws before wasting development cycles.

Grant Lee：“我们早上想到一个创意，就快速做出一个功能性原型，招募一批真正优质的潜在用户（他们没有任何既得利益），快速推出让人们试用。到下午，我们就已经在开展相当全面的实验了。”

在构思创意后的数小时内就构建功能性原型，保持开发速度，避免在浪费开发周期前发现可用性缺陷。

Direct User Feedback Loops

直接用户反馈循环

Gustaf Alstromer: "If I drill down what makes companies fail, it's quite simple. It's just like they don't talk to users, which means they don't find product market fit. And if they don't find product market fit, nothing else really matters."

Achieve product-market fit by talking to customers directly and immediately to learn if you are building something people actually want.

Gustaf Alstromer：“如果深究企业失败的原因，其实很简单。就是他们不与用户沟通，这意味着他们无法找到产品市场契合点。找不到产品市场契合点，其他一切都无关紧要。”

通过直接且及时地与客户沟通，了解你开发的产品是否是用户真正需要的，从而实现产品市场契合。

Workflow Compression

工作流程压缩

Oji Udezue: "So the zone of benefit works as a framework because people will not pay for things that don't either really shrink the workflow that they're doing or doesn't give them superpower. So the same amount of time, but twice as much output. But the most important thing is that it has to be noticeable."

A problem is only worth building for if your solution offers a visible and massive compression of the existing customer workflow.

Oji Udezue：“‘收益区间’框架之所以有效，是因为人们不会为那些既不能大幅简化现有工作流程，又不能赋予他们超强能力的产品付费。要么在相同时间内产出翻倍，要么最重要的是，这种改变必须是显著可见的。”

只有当你的解决方案能显著且大幅压缩客户现有工作流程时，这个问题才值得投入开发。

Templates & Frameworks

模板与框架

Four B2B Idea Validation Paths (How to validate your B2B startup idea) - A framework for choosing which validation strategy to use based on your context as a founder. Each path represents a different level of up-front investment and
B2B Idea Validation Interview Process (How to validate your B2B startup idea) - A synthesized process for conducting validation interviews based on patterns across multiple successful B2B founders
Four Signs Your B2B Idea Has Real Pull (How to validate your B2B startup idea) - A checklist of signals that indicate genuine market demand vs. polite but hollow interest
Vanta's Manual Validation Process (How to validate your B2B startup idea) - How Christina Cacioppo validated Vanta's idea by manually creating SOC 2 compliance reports before writing any code
Founding Hypothesis Scorecard (Introducing the Foundation Sprint: From the creators of the Design Sprint) - A scorecard with testable questions for each element of the Founding Hypothesis, used to systematically validate or invalidate your product strategy
Pre-Product Invoice Test (How to know if you've got product-market fit) - A pre-product PMF validation technique where you literally try to get potential customers to pay you before the product exists.
Ugly Baby Validation (1,000,000) - A framework for getting early validation on a new creative project by finding the right motivators
DoorDash's paloaltodelivery.com MVP (How the biggest consumer apps got their first 1,000 users) - How DoorDash validated demand with a simple website with PDF menus and printed flyers at Stanford

See

references/artifacts.md

for the full list with details.

四种B2B创意验证路径（如何验证你的B2B创业创意）- 一个帮助创始人根据自身情况选择验证策略的框架。每种路径代表不同的前期投入水平
B2B创意验证访谈流程（如何验证你的B2B创业创意）- 基于多位成功B2B创始人的经验总结出的验证访谈流程
B2B创意具备真实需求的四个信号（如何验证你的B2B创业创意）- 一份用于区分真实市场需求与礼貌性虚假兴趣的信号清单
Vanta的手动验证流程（如何验证你的B2B创业创意）- Christina Cacioppo如何在编写任何代码前，通过手动创建SOC 2合规报告来验证Vanta的创意
创始假设评分卡（介绍基础冲刺：来自设计冲刺的创造者）- 一份包含可测试问题的评分卡，针对创始假设的每个要素，用于系统性地验证或推翻你的产品策略
预产品发票测试（如何判断你是否已找到产品市场契合点）- 一种预产品阶段的PMF验证技巧，即尝试让潜在客户在产品尚未问世时就为其付费
“丑婴”验证法（1,000,000）- 一个通过找到正确激励因素，为新创意项目获取早期验证的框架
DoorDash的paloaltodelivery.com MVP（顶级消费应用如何获取首批1000名用户）- DoorDash如何通过一个带有PDF菜单的简单网站和斯坦福大学校园内的印刷传单来验证需求

详情请查看

references/artifacts.md

完整列表。

Questions to Help Users

用于帮助用户的问题

"What is the single most risky assumption that must be true for this idea to succeed?"
"Are you getting feedback from cold prospects or just people in your network who want to be nice?"
"How many steps does your solution remove from the user's current manual workflow?"
"If you had to launch a 'fake door' experiment tomorrow with zero backend, what would it look like?"
"Has a potential customer offered to pay for this before you have even built it?"
"What is the 'must-have' feature that, if missing, would cause the user to walk away immediately?"

“要让这个创意成功，哪一个单一假设是最具风险且必须成立的？”
“你是从陌生潜在用户那里获取反馈，还是仅从想讨好你的人脉圈那里得到反馈？”
“你的解决方案能为用户当前的手动工作流程减少多少步骤？”
“如果明天要开展一个无需后端的‘假门’实验，它会是什么样子？”
“有没有潜在客户在你还未开发产品时就提出要付费购买？”
“什么是‘必备’功能？如果缺少它，用户会立即放弃使用你的产品？”

Common Mistakes to Flag

需要指出的常见误区

Confusing Politeness with Validation - Mistaking 'this looks cool' for 'I will pay for this' leads to building products that lack real market pull.
Building Before Testing - Investing heavy engineering resources into a full backend before validating the front-end value proposition wastes months of time.
Relying on Warm Leads - Feedback from friends or family is biased and rarely provides the 'pure' signal needed to judge an idea's merit.
Averaging User Feedback - Failing to segment feedback between skeptics and early adopters can lead to a watered-down product that serves nobody well.

将礼貌当作验证 - 把“这个看起来很棒”误认为“我会为它付费”，会导致开发出缺乏真实市场需求的产品。
未测试先开发 - 在验证前端价值主张之前就投入大量工程资源构建完整后端，会浪费数月时间。
依赖熟人脉 - 来自朋友或家人的反馈存在偏见，几乎无法提供判断创意价值所需的“纯粹”信号。
平均用户反馈 - 未能区分怀疑者和早期采用者的反馈，可能导致产品被稀释，无法很好地服务任何用户群体。

Deep Dive

深入探索

For all 33 sourced insights from 31 guests, see

references/guest-insights.md

如需查看来自31位嘉宾的全部33条见解，请查看

references/guest-insights.md