lean-startup

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Note: This skill is independent analysis and commentary, not a reproduction of the original text. It synthesizes the book's core ideas with modern startup practice, surfaces where frameworks are outdated or incomplete, and integrates perspectives from adjacent disciplines. For the full argument and context, read the original book.

说明： 本技能为独立分析与评论，并非原文复刻。它结合了书籍核心观点与现代创业实践，指出框架过时或不完善之处，并整合了相关领域的视角。如需完整论点与背景，请阅读原版书籍。

The Lean Startup

精益创业（Lean Startup）

"The Lean Startup is not a collection of individual tactics. It is a principled approach to new product development." - Eric Ries

“精益创业不是零散策略的集合，而是新产品开发的系统化方法。”——Eric Ries

Should You Use This Skill?

是否应该使用本技能？

Are you building something under conditions of extreme uncertainty?
|-- YES --> Do you know who your customers are?
|   |-- NO  --> Start with Four Steps (Customer Discovery), use Lean
|   |           Startup for iteration speed within that process
|   +-- YES --> Do you have product/market fit?
|               |-- NO  --> THIS SKILL. Build-Measure-Learn loop.
|               +-- YES --> Use Crossing the Chasm for mainstream scaling
+-- NO  --> Are you optimizing an existing product in a known market?
            |-- YES --> Lean Startup principles apply (small batches,
            |           Five Whys) but you don't need the full framework
            +-- NO  --> Rethink what you're doing

Are you building something under conditions of extreme uncertainty?
|-- YES --> Do you know who your customers are?
|   |-- NO  --> Start with Four Steps (Customer Discovery), use Lean
|   |           Startup for iteration speed within that process
|   +-- YES --> Do you have product/market fit?
|               |-- NO  --> THIS SKILL. Build-Measure-Learn loop.
|               +-- YES --> Use Crossing the Chasm for mainstream scaling
+-- NO  --> Are you optimizing an existing product in a known market?
            |-- YES --> Lean Startup principles apply (small batches,
            |           Five Whys) but you don't need the full framework
            +-- NO  --> Rethink what you're doing

The Core Insight

核心洞见

Most startups fail not because they can't build a product, but because they build something nobody wants. The default response to failure is: we didn't plan well enough, execute hard enough, or have the right vision. Ries argues the real problem is the absence of a management framework designed for uncertainty.

A startup is: a human institution designed to create a new product or service under conditions of extreme uncertainty. This definition applies to garage founders, corporate intrapreneurs, and government innovators alike.

大多数创业公司失败，不是因为无法打造产品，而是因为打造了没人需要的产品。 面对失败的常规反应是：我们计划不够周全、执行不够努力，或者没有正确的愿景。Ries认为，真正的问题是缺乏针对不确定性的管理框架。

创业公司的定义是：在极端不确定性下，为创造新产品或服务而建立的人类组织。 这个定义适用于车库创业者、企业内部创新团队以及政府创新者。

The Five Principles

五大原则

Entrepreneurs are everywhere - any organization creating under uncertainty
Entrepreneurship is management - not just "a cool product" but a discipline
Validated learning - not "we learned a lot" but learning backed by empirical data
Build-Measure-Learn - turn ideas into products, measure response, learn whether to pivot or persevere
Innovation accounting - hold innovators accountable with a new kind of accounting designed for uncertainty

创业者无处不在——任何在不确定性环境下进行创造的组织
创业即管理——不只是“打造酷炫产品”，而是一门学科
验证性学习（Validated learning）——不是“我们学到了很多”，而是有实证数据支撑的学习
Build-Measure-Learn——将想法转化为产品，衡量用户反馈，学习判断是转型还是坚持
创新会计（Innovation accounting）——用专为不确定性设计的新型会计方法，让创新者承担责任

Build-Measure-Learn

Build-Measure-Learn循环

The fundamental activity loop. Minimize total time through the loop.

         IDEAS
        /      \
       /        \
  LEARN          BUILD
      \          /
       \        /
        DATA--PRODUCT
        (Measure)

Critical insight: Although the loop reads Build-Measure-Learn, you plan in reverse: figure out what you need to LEARN, determine what DATA will tell you that, then BUILD only what's needed to get that data.

"We need to focus our energies on minimizing the TOTAL time through this loop."

这是创业的核心活动循环。要尽可能缩短整个循环的总时长。

         IDEAS
        /      \
       /        \
  LEARN          BUILD
      \          /
       \        /
        DATA--PRODUCT
        (Measure)

关键洞见： 虽然循环顺序是Build-Measure-Learn，但你需要反向规划：先明确需要学习什么，再确定哪些数据能验证学习内容，最后只构建获取这些数据所需的产品部分。

“我们需要集中精力，缩短整个循环的总时长。”

Leap-of-Faith Assumptions

核心信念假设（Leap-of-Faith Assumptions）

Every startup rests on two untested assumptions:

Assumption	Question	How to Test
Value hypothesis	Does the product deliver value to customers who use it?	Engagement, retention, willingness to pay
Growth hypothesis	How will new customers discover the product?	Viral coefficient, referral rates, word-of-mouth tracking

Both must be tested empirically, not assumed. Use analogs (similar successes) and antilogs (similar failures) to sharpen assumptions before testing.

"The two most important assumptions are the value hypothesis and the growth hypothesis."

每个创业公司都基于两个未经验证的假设：

假设类型	问题	测试方法
Value hypothesis	产品是否为使用它的客户带来价值？	用户参与度、留存率、付费意愿
Growth hypothesis	新客户将如何发现产品？	病毒系数、推荐率、口碑追踪

这两个假设都必须通过实证测试，而非主观假设。在测试前，可使用类比案例（analogs）（类似成功案例）和反类比案例（antilogs）（类似失败案例）来细化假设。

“最重要的两个假设是价值假设（Value hypothesis）和增长假设（Growth hypothesis）。”

Minimum Viable Product (MVP)

最小可行产品（MVP）

The MVP is the fastest way to get through the Build-Measure-Learn loop with minimum effort. It is NOT the smallest product. It is the smallest experiment that tests your leap-of-faith assumptions.

WHAT AN MVP IS:                    WHAT AN MVP IS NOT:
- A learning vehicle               - A crappy v1.0
- Tests one specific assumption    - The smallest feature set
- Designed to maximize learning    - A prototype to show investors
- May lack features, polish, UX    - A proof of concept
- Can be embarrassingly simple     - A demo

MVP是以最小成本快速完成Build-Measure-Learn循环的方式。它不是最小化的产品，而是能测试核心信念假设的最小实验。

WHAT AN MVP IS:                    WHAT AN MVP IS NOT:
- A learning vehicle               - A crappy v1.0
- Tests one specific assumption    - The smallest feature set
- Designed to maximize learning    - A prototype to show investors
- May lack features, polish, UX    - A proof of concept
- Can be embarrassingly simple     - A demo

MVP Types

MVP类型

Type	When to Use	Example
Video	Value prop is hard to explain; gauge demand before building	Dropbox: 3-min demo video, signups went 5K to 75K overnight
Concierge	Deliver the value manually to one customer at a time	Food on the Table: CEO personally picked recipes and shopped for one family
Wizard of Oz	Automate the frontend, manual backend	Zappos: photos of shoes from stores, bought and shipped when ordered
Single-feature	Test one value driver with real usage	Groupon: WordPress blog + email, one deal per day in one city
Smoke test	Gauge demand before building anything	Landing page + signup form, measure conversion

类型	使用场景	示例
Video	价值主张难以解释；在开发前衡量需求	Dropbox：3分钟演示视频，一夜之间注册量从5000增至75000
Concierge	手动为单个客户交付价值	Food on the Table：CEO亲自为一个家庭挑选食谱并采购食材
Wizard of Oz	前端自动化，后端手动操作	Zappos：展示商店的鞋子照片，收到订单后再采购发货
Single-feature	通过真实使用测试单个价值驱动因素	Groupon：WordPress博客+邮件，每天在一个城市推出一个优惠活动
Smoke test	在开发前衡量需求	着陆页+注册表单，衡量转化率

MVP Quality Concerns

MVP质量顾虑

"If we do not know who the customer is, we do not know what quality is."

Customers don't care about quality dimensions you're imagining. Build the MVP, ship it, and let customer behavior (not opinions) tell you what quality means.

“如果我们不知道客户是谁，就不知道什么是质量。”

客户不会在意你设想的质量维度。构建MVP并上线，让客户行为（而非观点）告诉你质量的定义。

Innovation Accounting

创新会计（Innovation accounting）

Traditional accounting can't measure a startup. Revenue is near-zero. Forecasts are fiction. Innovation accounting provides an alternative.

传统会计无法衡量创业公司的进展：收入几乎为零，预测毫无依据。创新会计提供了替代方案。

Three Learning Milestones

三个学习里程碑

1. ESTABLISH THE BASELINE
   |-- Build an MVP
   |-- Get it in front of real customers
   +-- Measure current state of the engine (conversion, retention, revenue)

2. TUNE THE ENGINE
   |-- Run experiments to improve metrics from baseline toward ideal
   |-- Each experiment tests one assumption
   +-- Track whether changes actually move the numbers

3. PIVOT OR PERSEVERE
   |-- Is tuning working? Are you making progress toward the ideal?
   |-- YES --> Persevere. Keep tuning.
   +-- NO  --> Pivot. Change strategy fundamentally.

1. ESTABLISH THE BASELINE
   |-- Build an MVP
   |-- Get it in front of real customers
   +-- Measure current state of the engine (conversion, retention, revenue)

2. TUNE THE ENGINE
   |-- Run experiments to improve metrics from baseline toward ideal
   |-- Each experiment tests one assumption
   +-- Track whether changes actually move the numbers

3. PIVOT OR PERSEVERE
   |-- Is tuning working? Are you making progress toward the ideal?
   |-- YES --> Persevere. Keep tuning.
   +-- NO  --> Pivot. Change strategy fundamentally.

Vanity Metrics vs. Actionable Metrics

虚荣指标（Vanity Metrics）vs可落地指标（Actionable Metrics）

Vanity Metrics	Actionable Metrics
Total signups (cumulative)	Signups per cohort
Total revenue (gross)	Revenue per customer per cohort
Page views	Conversion rate by step
"Hits"	Retention by cohort
Registered users	Active users / registered users

The Three A's of Good Metrics:

Actionable - demonstrates clear cause and effect. If you change X, metric Y moves.
Accessible - everyone in the company can understand them. Use cohort reports, not cumulative.
Auditable - you can trace the data to real humans. Talk to the customers behind the numbers.

虚荣指标	可落地指标
总注册量（累计）	同期群注册量
总收入（毛收入）	同期群客户人均收入
页面浏览量	各环节转化率
“点击量”	同期群留存率
注册用户数	活跃用户/注册用户

优质指标的三大特征：

可落地（Actionable）——展示明确的因果关系。改变X，指标Y就会变化。
易理解（Accessible）——公司每个人都能理解。使用同期群报告，而非累计数据。
可审计（Auditable）——可追踪数据到真实用户。与数据背后的客户沟通。

Pivot or Persevere

转型（Pivot）还是坚持

A pivot is a structured course correction designed to test a new fundamental hypothesis about the product, strategy, and engine of growth. It is not failure. It is the mechanism that makes startups robust.

转型是为测试关于产品、战略和增长引擎的新核心假设而进行的结构化方向调整。它不是失败，而是让创业公司更稳健的机制。

The Pivot Meeting

转型会议

Hold regularly (monthly or quarterly). Bring product development AND business leadership. Review:

Are our experiments moving metrics toward the ideal model?
Is our progress sufficient given the time and resources invested?
What have we learned about our assumptions?

定期召开（每月或每季度）。需产品开发和业务领导共同参与。回顾以下内容：

我们的实验是否让指标向理想模型推进？
投入时间和资源后，我们的进展是否足够？
我们对假设有了哪些新认知？

Ten Types of Pivot

十大转型类型

Pivot	Description
Zoom-in	A single feature becomes the whole product
Zoom-out	The whole product becomes a single feature of something larger
Customer segment	Same product, different customer
Customer need	Same customer, different problem
Platform	Change from application to platform (or vice versa)
Business architecture	Switch between high-margin/low-volume and low-margin/high-volume
Value capture	Change how you make money (monetization model)
Engine of growth	Switch between viral, sticky, or paid growth
Channel	Change distribution mechanism
Technology	Same solution, different technology

转型类型	描述
Zoom-in	单个功能成为整个产品
Zoom-out	整个产品成为更大产品的单个功能
Customer segment	产品不变，目标客户群体改变
Customer need	客户群体不变，解决的问题改变
Platform	从应用程序转为平台（反之亦然）
Business architecture	在高利润低销量和低利润高销量模式间切换
Value capture	改变盈利方式（变现模型）
Engine of growth	在病毒式、粘性式或付费式增长引擎间切换
Channel	改变分销渠道
Technology	解决方案不变，技术栈改变

Runway = Pivots Remaining

runway = 剩余转型次数

"The true measure of runway is how many pivots a startup has left."

Not months of cash. A startup that can test more hypotheses before running out of money has a longer runway than one burning cash on a single bet.

“runway的真正衡量标准是创业公司剩余的转型次数。”

不是现金能支撑的月数。在烧完钱前能测试更多假设的创业公司，比把现金押在单一赌注上的公司拥有更长的runway。

Three Engines of Growth

三大增长引擎

Every startup's growth is powered by one dominant engine. Focus on ONE.

Engine	Mechanic	Key Metric	Grows When...
Sticky	High retention. Existing customers keep using.	Churn rate	New customer acquisition > churn
Viral	Customers recruit more customers as a side effect of usage	Viral coefficient (k)	k > 1.0 (each user brings >1 new user)
Paid	Spend money to acquire customers profitably	LTV vs. CPA	LTV > CPA (lifetime value exceeds cost to acquire)

"Startups don't starve; they drown." - in too many simultaneous growth strategies.

每个创业公司的增长都由一个主导引擎驱动。需专注于一个引擎。

引擎类型	运作机制	核心指标	增长条件
Sticky	高留存率。现有客户持续使用	流失率	新客户获取量 > 流失量
Viral	用户在使用过程中自发推荐新客户	病毒系数（k）	k > 1.0（每个用户带来超过1个新用户）
Paid	花钱盈利性地获取客户	客户终身价值（LTV）vs客户获取成本（CPA）	LTV > CPA（终身价值超过获取成本）

“创业公司不会饿死，而是淹死在同时推进的太多增长策略里。”

Engine Selection

引擎选择

Is your product inherently shareable / visible to non-users?
|-- YES --> Test VIRAL engine first
+-- NO  --> Do customers use it repeatedly (daily/weekly)?
            |-- YES --> Test STICKY engine first
            +-- NO  --> Test PAID engine first

Important: engines eventually run out. When they do, pivot or find a new engine.

Is your product inherently shareable / visible to non-users?
|-- YES --> Test VIRAL engine first
+-- NO  --> Do customers use it repeatedly (daily/weekly)?
            |-- YES --> Test STICKY engine first
            +-- NO  --> Test PAID engine first

Important: engines eventually run out. When they do, pivot or find a new engine.

Small Batches

小批量生产（Small Batches）

Borrowed from Toyota Production System. Smaller batches = faster learning = fewer wasted resources.

Large Batch	Small Batch
Build everything, then test	Build one thing, test immediately
Defects found late, expensive to fix	Defects found early, cheap to fix
Long feedback cycles	Short feedback cycles
Satisfying (feels productive)	Uncomfortable (feels slow)
Death spiral: rework compounds	Continuous flow: rework is instant

"The biggest advantage of working in small batches is that quality problems can be identified much sooner."

借鉴自丰田生产系统。批量越小，学习速度越快，资源浪费越少。

大批量生产	小批量生产
先构建所有内容，再测试	先构建单个模块，立即测试
缺陷发现晚，修复成本高	缺陷发现早，修复成本低
反馈周期长	反馈周期短
有成就感（感觉高效）	令人不适（感觉缓慢）
死亡螺旋：返工不断累积	持续流动：返工即时处理

“小批量生产的最大优势是能更早发现质量问题。”

The Large-Batch Death Spiral

大批量死亡螺旋

Large batches look efficient but create a death spiral: the bigger the batch, the longer to test, the more rework, the bigger the next batch needs to be to "catch up," the longer to test...

大批量生产看似高效，但会形成死亡螺旋：批量越大，测试周期越长，返工越多，下一批量就需要更大才能“赶上进度”，测试周期也会更长……

Pull, Don't Push (from Toyota JIT)

拉动式生产，而非推动式（源自丰田JIT）

Work in progress is inventory. In startups, features built but not validated are WIP. Only build what's needed for the next experiment.

在制品是库存。对于创业公司，已构建但未验证的功能就是在制品。只构建下一个实验所需的内容。

Five Whys

五问法（Five Whys）

Adapted from Taiichi Ohno's Toyota Production System. At the root of every technical problem is a human problem.

改编自丰田生产系统的大野耐一方法。每个技术问题的根源都是人的问题。

The Method

方法

Ask "Why?" five times to trace symptoms to root causes. Make a proportional investment at each level - small fix for small problem, bigger investment for deeper cause.

连续问五次“为什么？”，从表象追溯到根本原因。在每个层面进行成比例的投入——小问题小修复，深层原因大投入。

The Five Blames (Anti-Pattern)

五责法（反模式）

When Five Whys goes wrong, it becomes finger-pointing. Prevent this:

Everyone affected by the problem must be in the room
Senior people go first with "shame on us for making it so easy to make that mistake"
Focus on bad process, not bad people
Appoint a Five Whys master
Start with a narrow, specific class of problems
Never start with legacy "baggage" problems

当五问法被错误使用时，会变成指责游戏。避免这种情况：

所有受问题影响的人必须到场
先由资深人员表态：“是我们的问题，让这个错误容易发生”
聚焦于糟糕的流程，而非犯错的人
指定五问法负责人
从狭窄、特定类型的问题开始
不要从遗留的“历史包袱”问题入手

Decision Trees

决策树

"What should our MVP be?"

“我们的MVP应该是什么样的？”

What do you need to LEARN?
|-- "Do customers want this at all?"
|   +-- Smoke test (landing page) or Video MVP
|-- "Will customers pay for this?"
|   +-- Concierge or Wizard of Oz (deliver manually, charge real money)
|-- "Can we build the technology?"
|   +-- Technical prototype (not an MVP - engineering risk, not market risk)
+-- "Which features matter?"
    +-- Single-feature MVP + split testing

What do you need to LEARN?
|-- "Do customers want this at all?"
|   +-- Smoke test (landing page) or Video MVP
|-- "Will customers pay for this?"
|   +-- Concierge or Wizard of Oz (deliver manually, charge real money)
|-- "Can we build the technology?"
|   +-- Technical prototype (not an MVP - engineering risk, not market risk)
+-- "Which features matter?"
    +-- Single-feature MVP + split testing

"Should we pivot?"

“我们应该转型吗？”

Are experiments moving metrics toward the ideal?
|-- YES, meaningfully --> Persevere. Keep tuning.
|-- YES, but very slowly --> Investigate. Are you out of easy optimizations?
|   |-- YES --> Consider pivot
|   +-- NO  --> Keep tuning, but set a deadline
+-- NO --> Have you exhausted experiment ideas for current strategy?
          |-- YES --> PIVOT. Change a fundamental hypothesis.
          +-- NO  --> Run more experiments, but set a time box.

After pivoting:
- Acceleration test: is the new direction producing faster learning?
- If MVP cycles aren't getting shorter, something is still wrong.

Are experiments moving metrics toward the ideal?
|-- YES, meaningfully --> Persevere. Keep tuning.
|-- YES, but very slowly --> Investigate. Are you out of easy optimizations?
|   |-- YES --> Consider pivot
|   +-- NO  --> Keep tuning, but set a deadline
+-- NO --> Have you exhausted experiment ideas for current strategy?
          |-- YES --> PIVOT. Change a fundamental hypothesis.
          +-- NO  --> Run more experiments, but set a time box.

After pivoting:
- Acceleration test: is the new direction producing faster learning?
- If MVP cycles aren't getting shorter, something is still wrong.

"Are we using vanity metrics?"

“我们在使用虚荣指标吗？”

Does this metric go up and to the right no matter what you do?
|-- YES --> It's vanity. Switch to cohort-based or per-customer metrics.
+-- NO  --> Can you trace a specific change to movement in this metric?
            |-- YES --> It's actionable. Keep it.
            +-- NO  --> Probably vanity. Test with a split experiment.

Does this metric go up and to the right no matter what you do?
|-- YES --> It's vanity. Switch to cohort-based or per-customer metrics.
+-- NO  --> Can you trace a specific change to movement in this metric?
            |-- YES --> It's actionable. Keep it.
            +-- NO  --> Probably vanity. Test with a split experiment.

Critical Numbers & Rules of Thumb

关键数字与经验法则

Number	Rule
2	Leap-of-faith assumptions to test (value + growth)
3	Learning milestones (baseline, tune, pivot-or-persevere)
3	Engines of growth (sticky, viral, paid)
1	Engine to focus on at a time
>1.0	Viral coefficient needed for viral growth
LTV > CPA	Required for paid engine to work
5	Whys to ask for root cause analysis
10	Types of pivot
50	Deploys per day at IMVU (continuous deployment)

数字	法则
2	需要测试的核心信念假设（价值+增长）
3	学习里程碑（基线、优化、转型或坚持）
3	增长引擎（粘性、病毒、付费）
1	同一时间需专注的引擎数量
>1.0	病毒式增长所需的病毒系数
LTV > CPA	付费引擎有效的必要条件
5	根本原因分析需问的“为什么”次数
10	转型类型数量
50	IMVU每日部署次数（持续部署）

Common Failure Patterns

常见失败模式

Pattern	Mechanism	Cure
Achieving failure	Successfully executing a plan nobody validated	Build-Measure-Learn loop from day 1
Vanity metrics	Dashboard goes up-and-right but business isn't growing	Cohort analysis, actionable metrics, split tests
Premature optimization	Tuning features before validating the problem exists	Ship MVP first, optimize after baseline established
Large-batch death spiral	Big releases, late feedback, compounding rework	Small batches, continuous deployment
Theater of learning	"We learned a lot" with no data to prove it	Innovation accounting; learning must change future behavior
Success theater	Cherry-picking metrics to look good	Three A's: Actionable, Accessible, Auditable
Pivot too late	Emotional attachment to current strategy delays pivot	Regular pivot-or-persevere meetings with hard data
Pivot too fast	Pivoting before giving experiments time to produce data	Set time boxes; finish experiments before deciding
Feature factory	Shipping features as a proxy for progress	Tie every feature to a hypothesis and a metric

模式	机制	解决方法
成功式失败	成功执行了未经验证的计划	从第一天开始使用Build-Measure-Learn循环
虚荣指标	数据面板持续上升，但业务未增长	同期群分析、可落地指标、拆分测试
过早优化	在验证问题存在前就优化功能	先上线MVP，建立基线后再优化
大批量死亡螺旋	大版本发布、反馈延迟、返工累积	小批量生产、持续部署
学习表演	“我们学到了很多”但无数据支撑	创新会计；学习必须改变未来行为
成功表演	挑选数据让自己看起来不错	遵循三大特征：可落地、易理解、可审计
转型过晚	对当前策略的情感依恋延迟了转型	定期召开基于硬数据的转型或坚持会议
转型过快	在实验产生数据前就转型	设置时间限制；完成实验后再做决定
功能工厂	以发布功能作为进展的替代指标	将每个功能与假设和指标绑定

Modern Relevance (2011 --> 2026)

现代相关性（2011 --> 2026）

Where Lean Startup Still Applies

精益创业仍适用的场景

Pre-product/market-fit startups of any kind
Corporate innovation teams testing new business lines
Hardware and physical products (with longer cycle times)
Any team that doesn't know if what they're building will work

未达成产品-市场匹配的各类创业公司
测试新业务线的企业创新团队
硬件和实体产品（周期更长）
任何不确定所建产品是否有用的团队

Where It Shows Its Age

精益创业显露出局限性的场景

AI-native products - the feedback loop can be automated in ways Ries didn't anticipate
PLG/viral-first products - the MVP concept is well-understood; the harder question is distribution
Hypergrowth VC model - "runway = pivots remaining" conflicts with "blitzscale or die" pressure
No-code/low-code - building an MVP is now so cheap that the bottleneck is finding users, not building product

AI原生产品——反馈循环的自动化程度超出Ries的预期
PLG/病毒优先产品——MVP概念已被广泛理解；更难的是分销问题
高速增长VC模式——“runway=剩余转型次数”与“快速扩张否则死亡”的压力冲突
无代码/低代码——构建MVP的成本极低，瓶颈变为寻找用户而非打造产品

What Ries Got Permanently Right

Ries永久正确的观点

Validated learning as the unit of progress, not features or code
Build-Measure-Learn as the fundamental loop
MVPs as experiments, not small products
Vanity metrics as the default trap
Pivots as structured hypothesis changes, not random flailing
Small batches beat large batches in nearly every context
Five Whys for proportional investment in root causes

以验证性学习而非功能或代码作为进展单位
Build-Measure-Learn作为核心循环
MVP是实验而非小型产品
虚荣指标是默认陷阱
转型是结构化的假设变更而非随机试错
几乎所有场景下小批量都优于大批量
五问法用于根本原因的成比例投入

Supporting Files

配套文件

frameworks.md - Build-Measure-Learn detailed breakdown, leap-of-faith assumptions, MVP selection, innovation accounting milestones, vanity vs. actionable metrics, pivot catalog, engines of growth mechanics, small batches, Five Whys, innovation sandbox, adaptive organization
cases.md - IMVU (founding story + continuous deployment), Zappos (Wizard of Oz MVP), Dropbox (video MVP), Groupon (MVP origin), Grockit (innovation accounting), Votizen (3 pivots with metrics), Wealthfront (platform pivot), QuickBooks (large company transformation), IGN Entertainment (Five Whys), SGW Designworks (physical product small batches)
examples.md - MVP selection worksheet, innovation accounting setup template, pivot-or-persevere meeting template, engine of growth diagnostic, Five Whys session template, cohort analysis template, Build-Measure-Learn cycle planner
integration.md - Relationship to Four Steps (Lean Startup is direct descendant), relationship to Mom Test (conversation technique for the Learn phase), relationship to Crossing the Chasm (Lean Startup stops at product/market fit), conflicts with $100M Offers (validation-first vs. offer-first), master sequence

frameworks.md——Build-Measure-Learn详细分解、核心信念假设、MVP选择、创新会计里程碑、虚荣指标vs可落地指标、转型目录、增长引擎机制、小批量生产、五问法、创新沙盒、自适应组织
cases.md——IMVU（创始故事+持续部署）、Zappos（Wizard of Oz MVP）、Dropbox（视频MVP）、Groupon（MVP起源）、Grockit（创新会计）、Votizen（3次带数据的转型）、Wealthfront（平台转型）、QuickBooks（大企业转型）、IGN Entertainment（五问法）、SGW Designworks（实体产品小批量生产）
examples.md——MVP选择工作表、创新会计设置模板、转型或坚持会议模板、增长引擎诊断工具、五问法会话模板、同期群分析模板、Build-Measure-Learn循环规划器
integration.md——与四步法的关系（精益创业是直接衍生）、与Mom Test的关系（学习阶段的沟通技巧）、与《跨越鸿沟》的关系（精益创业止步于产品-市场匹配）、与《百万美元报价》的冲突（验证优先vs报价优先）、完整应用序列

Honest Scope of the Book

书籍的真实适用范围

Published: 2011
Examples: Mostly 2004-2010 tech (IMVU, Dropbox, Groupon, Zappos, Votizen). Some are now household names; others pivoted or died.
Empirical base: Author's experience at IMVU + consulting/advising. Anecdotal case studies, not statistical research. Ries acknowledges this directly.
Where it shines: Early-stage startups, corporate innovation, any team testing whether something should exist.
Where it's weak: Post-product/market-fit scaling, marketplace dynamics, deep infrastructure products where MVP approach is dangerous (medical devices, aircraft software). The book is light on HOW to talk to customers (use Mom Test) and silent on Market Type (use Four Steps).
Intellectual lineage: Direct descendant of Steve Blank's Four Steps to the Epiphany + Toyota Production System (Taiichi Ohno). Ries was Blank's student and implemented Customer Development at IMVU. The Build-Measure-Learn loop owes a lot to Boyd's OODA loop.

出版时间： 2011年
案例： 主要是2004-2010年的科技公司（IMVU、Dropbox、Groupon、Zappos、Votizen）。部分如今已是家喻户晓的品牌，部分已转型或倒闭。
实证基础： 作者在IMVU的经验+咨询/顾问经历。基于轶事案例研究，而非统计研究。Ries直接承认这一点。
优势场景： 早期创业公司、企业创新、任何测试产品是否应该存在的团队。
劣势场景： 达成产品-市场匹配后的扩张、市场动态、MVP方法存在风险的深度基础设施产品（医疗设备、飞机软件）。本书在如何与客户沟通方面内容较少（请使用Mom Test），且未提及市场类型（请使用四步法）。
知识传承： 直接源自Steve Blank的《顿悟四步法》+丰田生产系统（大野耐一）。Ries是Blank的学生，并在IMVU实施了客户开发方法。Build-Measure-Learn循环很大程度上借鉴了Boyd的OODA循环。