Back to Details

lean-startup

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Lean Startup Method

Lean Startup 方法论

This skill provides startup advice based on Eric Ries' Lean Startup methodology, emphasizing rapid experimentation, validated learning, and iterative product development.
本技能基于Eric Ries的Lean Startup方法论提供创业建议，强调快速实验、验证性学习和迭代式产品开发。

Core Philosophy

核心理念

"The only way to win is to learn faster than anyone else." - Eric Ries
The Lean Startup is a scientific approach to creating and managing startups that gets desired products into customers' hands faster. It's about testing your vision continuously, adapting and adjusting before it's too late.
"取胜的唯一途径就是比任何人都更快地学习。" - Eric Ries
Lean Startup 是一种创建和管理创业公司的科学方法，能够更快地将符合需求的产品交付到客户手中。它的核心是持续测试你的愿景，及时做出调整和适配，避免为时已晚。

The Build-Measure-Learn Loop

Build-Measure-Learn 循环

The fundamental activity of a startup is to turn ideas into products, measure how customers respond, and then learn whether to pivot or persevere. All successful startup processes should be geared to accelerate this feedback loop.
   IDEAS
     ↓
   BUILD → PRODUCT
     ↓
  MEASURE → DATA
     ↓
   LEARN → IDEAS (repeat)
创业公司的核心活动是将想法转化为产品，衡量客户的反馈，然后学习决定是Pivot（转型）还是坚持。所有成功的创业流程都应致力于加速这一反馈循环。
   IDEAS
     ↓
   BUILD → PRODUCT
     ↓
  MEASURE → DATA
     ↓
   LEARN → IDEAS (repeat)

How the Loop Works:

循环运作方式：

  1. IDEAS (Learn): Start with hypotheses about your business
  2. BUILD: Create minimum viable product (MVP) to test hypotheses
  3. MEASURE: Collect data on how customers actually behave
  4. LEARN: Validate or invalidate your hypotheses
  5. Decide: Pivot (change course) or Persevere (stay the course)
  6. Repeat: Continue the cycle faster and faster
The Goal: Minimize total time through the loop (cycle time).
  1. IDEAS（学习）： 从关于业务的假设开始
  2. BUILD： 创建最小可行产品（MVP）来测试假设
  3. MEASURE： 收集客户实际行为的数据
  4. LEARN： 验证或推翻你的假设
  5. 决策： Pivot（转型）或坚持现有方向
  6. 重复： 持续加快循环速度
目标： 最小化完成整个循环的总时间（周期时间）。

Five Principles of Lean Startup

Lean Startup 的五大原则

1. Entrepreneurs Are Everywhere

1. 创业者无处不在

You don't need a garage or venture capital to be a startup. A startup is a human institution designed to create new products/services under conditions of extreme uncertainty.
你不需要车库或风险投资就能成为创业者。创业公司是一个在极端不确定条件下，旨在创造新产品或服务的人类组织。

2. Entrepreneurship Is Management

2. 创业即管理

A startup is an institution, not just a product. It requires management specifically geared to its context of extreme uncertainty.
创业公司是一个组织，而不仅仅是一款产品。它需要针对极端不确定性环境的专属管理方式。

3. Validated Learning

3. 验证性学习

Startups exist to learn how to build a sustainable business. This learning can be validated scientifically by running frequent experiments.
创业公司的存在意义是学习如何打造可持续的业务。这种学习可以通过频繁开展实验来进行科学验证。

4. Build-Measure-Learn

4. Build-Measure-Learn

The fundamental activity is turning ideas into products, measuring customer response, and learning whether to pivot or persevere. Minimize total time through the loop.
核心活动是将想法转化为产品，衡量客户反馈，然后学习决定是Pivot还是坚持。最小化完成整个循环的总时间。

5. Innovation Accounting

5. 创新会计

Hold innovators accountable by focusing on the boring stuff: how to measure progress, set milestones, and prioritize work. This requires new accounting designed for startups.
通过关注看似枯燥的内容来让创新者承担责任：如何衡量进展、设定里程碑以及确定工作优先级。这需要为创业公司量身定制的新型会计方法。

Validated Learning

验证性学习

Validated learning is the process of demonstrating empirically that your team has discovered valuable truths about the startup's present and future business prospects.
验证性学习是指通过实证方式证明你的团队已经发现了关于创业公司当前和未来业务前景的有价值真相的过程。

Not Validated Learning:

非验证性学习：

  • "We shipped features on time"
  • "We executed our plan perfectly"
  • "We built what we said we'd build"
  • "Customers said they liked it"
  • "我们按时交付了功能"
  • "我们完美执行了计划"
  • "我们构建了承诺的产品"
  • "客户说他们喜欢这款产品"

Validated Learning:

验证性学习：

  • "We proved customers will pay for feature X"
  • "We discovered customers don't care about feature Y"
  • "We learned customer segment A converts 5x better than B"
  • "We validated our pricing hypothesis"
  • "我们证明客户愿意为功能X付费"
  • "我们发现客户并不关心功能Y"
  • "我们了解到客户群体A的转化率是群体B的5倍"
  • "我们验证了定价假设"

How to Validate:

验证方法：

  1. State a hypothesis: "If we add feature X, conversion will increase 10%"
  2. Design an experiment: A/B test with and without feature X
  3. Define success metrics: Measure actual conversion rate
  4. Run the experiment: Collect real data
  5. Learn: Did the hypothesis prove true? Why or why not?
  6. Decide: Build more, pivot, or kill the feature
Key Question: What did you learn that you couldn't have learned more cheaply/quickly?
  1. 提出假设： "如果我们添加功能X，转化率将提升10%"
  2. 设计实验： 进行有无功能X的A/B测试
  3. 定义成功指标： 衡量实际转化率
  4. 开展实验： 收集真实数据
  5. 学习： 假设是否成立？原因是什么？
  6. 决策： 继续开发、转型或放弃该功能
关键问题： 你学到了什么，而这些内容无法通过更廉价/快速的方式获得？

Minimum Viable Product (MVP)

最小可行产品（MVP）

The MVP is the version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.
MVP是新产品的一个版本，能够让团队用最少的精力收集到关于客户的最多验证性学习内容。

What an MVP Is:

MVP的定义：

  • Minimum: Smallest thing you can build to test a hypothesis
  • Viable: Enough to get meaningful learning
  • Product: Something customers can interact with
  • 最小化： 用于测试假设的最简版本
  • 可行性： 足以获得有意义的学习内容
  • 产品： 客户可以与之互动的实体

What an MVP Is NOT:

MVP的误区：

  • A beta version with fewer features
  • A prototype that doesn't reach real customers
  • An excuse for poor quality
  • A half-baked product
  • 不是功能更少的beta版本
  • 不是无法触达真实客户的原型
  • 不是质量低劣的借口
  • 不是半成品

Types of MVPs:

MVP的类型：

1. Concierge MVP

1. 礼宾式MVP

Manually deliver your service to customers while you learn what to build.
Example: Food on the Table started with founder manually creating meal plans for individual customers before building software.
When to use: Complex service where you need to understand customer workflow deeply.
在学习需要构建什么的过程中，手动为客户提供服务。
示例： Food on the Table 最初由创始人手动为每位客户制定用餐计划，之后才开发了相关软件。
适用场景： 复杂服务，需要深入了解客户工作流程。

2. Wizard of Oz MVP

2. 绿野仙踪式MVP

Customers think they're using a fully automated product, but you're doing the work manually behind the scenes.
Example: Zappos started by posting shoe photos online, then buying from retail stores when orders came in.
When to use: You need to validate demand before building expensive automation.
客户认为自己在使用全自动化产品，但背后是你手动完成所有工作。
示例： Zappos 最初在网上发布鞋子照片，接到订单后再从零售店采购。
适用场景： 需要在构建昂贵的自动化系统之前验证需求。

3. Landing Page MVP

3. 着陆页MVP

Single page describing your product with email signup or pre-order button.
Example: Dropbox famous video demo that led to 75,000 signups overnight.
When to use: Testing initial interest before building anything.
单个页面描述你的产品，包含邮件注册或预购按钮。
示例： Dropbox 著名的演示视频一夜之间获得了75,000个注册用户。
适用场景： 在构建任何产品之前测试初始兴趣。

4. Single-Feature MVP

4. 单功能MVP

Build only the core feature that delivers the primary value proposition.
Example: Twitter started as just status updates, nothing else.
When to use: You have multiple feature ideas but need to validate core value first.
仅构建能够传递核心价值主张的核心功能。
示例： Twitter 最初仅支持状态更新，没有其他功能。
适用场景： 有多个功能想法，但需要先验证核心价值。

5. Piecemeal MVP

5. 拼凑式MVP

Stitch together existing tools/services to deliver your value prop without building custom software.
Example: Groupon started using WordPress + AppleScript + email.
When to use: You want to validate the business model before investing in technology.
整合现有工具/服务来传递价值主张，无需构建自定义软件。
示例： Groupon 最初使用WordPress + AppleScript + 邮件来运营。
适用场景： 希望在投入技术开发之前验证商业模式。

MVP Development Process:

MVP开发流程：

  1. Identify riskiest assumption (usually: will customers want this?)
  2. Design minimum experiment to test that assumption
  3. Define success criteria before building
  4. Build only what's needed to run the experiment
  5. Get it in front of real customers ASAP
  6. Measure actual behavior (not opinions)
  7. Learn and iterate or pivot
Remember: If you're not embarrassed by your first version, you launched too late.
  1. 识别最具风险的假设（通常是：客户是否需要这个产品？）
  2. 设计最小实验来测试该假设
  3. 在构建前定义成功标准
  4. 仅构建开展实验所需的内容
  5. 尽快将其交付给真实客户
  6. 衡量实际行为（而非观点）
  7. 学习并迭代或转型
记住： 如果你的第一个版本没有让你感到尴尬，说明你发布得太晚了。

Innovation Accounting

创新会计

Traditional accounting doesn't work for startups because:
  • Revenue is often zero or too low to be meaningful
  • Traditional metrics measure execution, not learning
  • They don't help you make pivot/persevere decisions
传统会计不适用于创业公司，原因如下：
  • 收入通常为零或低到没有意义
  • 传统指标衡量的是执行情况，而非学习成果
  • 它们无法帮助你做出转型或坚持的决策

The Three Steps of Innovation Accounting:

创新会计的三个步骤：

Step 1: Establish the Baseline

步骤1：建立基准

Use an MVP to collect real data on where you are today.
Metrics to establish:
  • Current conversion rates
  • Customer acquisition cost (CAC)
  • Activation rate
  • Retention rate
  • Referral rate
  • Revenue per customer
使用MVP收集关于当前状态的真实数据。
需要建立的指标：
  • 当前转化率
  • 客户获取成本（CAC）
  • 激活率
  • 留存率
  • 推荐率
  • 每客户收入

Step 2: Tune the Engine

步骤2：优化引擎

Make small improvements and see if metrics move in the right direction.
What to measure:
  • Did the change improve the metric?
  • By how much?
  • Was it statistically significant?
  • What did we learn?
进行小幅改进，观察指标是否朝着正确方向变化。
需要衡量的内容：
  • 变化是否提升了指标？
  • 提升幅度是多少？
  • 是否具有统计显著性？
  • 我们学到了什么？

Step 3: Pivot or Persevere

步骤3：转型或坚持

If you can't improve metrics enough to achieve business goals, it's time to pivot.
Decision criteria:
  • Are we making sufficient progress?
  • Is the rate of improvement fast enough?
  • Can we reach our goals with current trajectory?
如果无法充分提升指标以实现业务目标，就该考虑转型了。
决策标准：
  • 我们是否取得了足够的进展？
  • 改进速度是否足够快？
  • 按照当前轨迹，我们能否实现目标？

Actionable Metrics vs. Vanity Metrics

可行动指标 vs. 虚荣指标

Vanity Metrics (Avoid):

虚荣指标（应避免）：

  • Total registered users: Doesn't show if they're active or paying
  • Total page views: Doesn't indicate engagement quality
  • Number of downloads: Doesn't show retention
  • Social media followers: Doesn't correlate to business value
Why they're dangerous: They make you feel good but don't help you make decisions.
  • 总注册用户数： 无法体现用户是否活跃或付费
  • 总页面浏览量： 无法反映参与质量
  • 下载量： 无法体现留存情况
  • 社交媒体粉丝数： 与业务价值无直接关联
危险之处： 它们让你感觉良好，但无法帮助你做出决策。

Actionable Metrics (Use):

可行动指标（应使用）：

  • Active users (DAU/MAU): Who's actually using the product?
  • Cohort retention: Do users come back over time?
  • Customer lifetime value (LTV): How much is a customer worth?
  • Customer acquisition cost (CAC): What does it cost to acquire a customer?
  • Viral coefficient: How many new users does each user bring?
  • Revenue growth rate: How fast are you growing?
Why they're useful: They help you make concrete decisions and understand cause-and-effect.
  • 活跃用户（日活/月活）： 谁真正在使用产品？
  • 群组留存率： 用户是否会回头使用？
  • 客户生命周期价值（LTV）： 一个客户的价值是多少？
  • 客户获取成本（CAC）： 获取一个客户的成本是多少？
  • 病毒系数： 每个用户能带来多少新用户？
  • 收入增长率： 增长速度有多快？
优势： 它们帮助你做出具体决策，理解因果关系。

Making Metrics Actionable:

让指标具备可行动性：

Bad: "Traffic increased 20% this month"
  • Why did it increase?
  • Which traffic sources?
  • Did those visitors convert?
  • Can we repeat this?
Good: "Changed headline on landing page, which increased conversion from 2% to 3.5% (statistically significant, p<0.05), resulting in 50% more trial signups"
  • Clear cause and effect
  • Measurable result
  • Repeatable action
糟糕的表述： "本月流量增长了20%"
  • 为什么增长？
  • 来自哪些流量来源？
  • 这些访客是否转化？
  • 我们能否复制这一成果？
优秀的表述： "修改了着陆页的标题，将转化率从2%提升至3.5%（统计显著，p<0.05），导致试用注册量增加了50%"
  • 明确的因果关系
  • 可衡量的结果
  • 可重复的行动

The Pivot

Pivot（转型）

A pivot is a structured course correction designed to test a new fundamental hypothesis about the product, strategy, or engine of growth.
**Pivot（转型）**是一种旨在测试关于产品、战略或增长引擎的新核心假设的结构化方向调整。

When to Pivot:

何时转型：

Signs it's time:
  • Decreasing effectiveness of product experiments
  • Metrics aren't improving despite multiple iterations
  • Customer feedback consistently points in different direction
  • You're running out of ideas to test current hypothesis
  • The market or technology has fundamentally shifted
Don't pivot if:
  • You haven't given current approach enough time/iterations
  • You're pivoting based on gut feeling vs. data
  • You're pivoting to avoid hard work
  • One customer said they want something different
信号：
  • 产品实验的有效性下降
  • 经过多次迭代后指标仍未提升
  • 客户反馈持续指向不同方向
  • 针对当前假设的测试想法已耗尽
  • 市场或技术发生根本性转变
不要转型的情况：
  • 尚未给当前方法足够的时间/迭代次数
  • 基于直觉而非数据转型
  • 为了逃避艰苦工作而转型
  • 仅一位客户表示需要其他功能

Types of Pivots:

转型类型：

1. Zoom-In Pivot

1. 聚焦式转型

What was previously a single feature becomes the whole product.
Example: Flickr started as a multiplayer game; photo-sharing feature became the product.
原本的单一功能成为整个产品。
示例： Flickr 最初是一款多人游戏；照片分享功能后来成为了核心产品。

2. Zoom-Out Pivot

2. 拓展式转型

What was the whole product becomes a single feature of a larger product.
Example: YouTube started as a dating site with video profiles.
原本的整个产品成为更大产品的单一功能。
示例： YouTube 最初是一个带有视频资料的约会网站。

3. Customer Segment Pivot

3. 客户群体转型

Product solves a real problem but for a different customer than originally anticipated.
Example: Groupon pivoted from activism platform to local deals.
产品确实解决了真实问题，但服务的客户与最初预期不同。
示例： Groupon 从行动主义平台转型为本地优惠平台。

4. Customer Need Pivot

4. 客户需求转型

Target customer has a different problem than you originally anticipated.
Example: Potbelly Sandwich started as an antique store that sold sandwiches; realized customers wanted sandwiches, not antiques.
目标客户的问题与你最初预期不同。
示例： Potbelly Sandwich 最初是一家卖三明治的古董店；后来发现客户想要的是三明治，而非古董。

5. Platform Pivot

5. 平台转型

Change from application to platform or vice versa.
Example: Shopify started as online store for snowboards, became e-commerce platform.
从应用程序转为平台，或反之。
示例： Shopify 最初是一个滑雪板在线商店，后来成为电商平台。

6. Business Architecture Pivot

6. 业务架构转型

Switch between high margin/low volume (complex sales) and low margin/high volume (volume operations).
Example: Moving from enterprise B2B to self-service B2C.
在高利润低销量（复杂销售）和低利润高销量（规模化运营）之间切换。
示例： 从企业级B2B转向自助式B2C。

7. Value Capture Pivot

7. 价值获取转型

Change how you monetize or capture value.
Example: Switching from freemium to paid-only, or advertising to subscription.
改变变现或获取价值的方式。
示例： 从免费增值模式转为付费模式，或从广告模式转为订阅模式。

8. Engine of Growth Pivot

8. 增长引擎转型

Change growth strategy between viral, sticky, or paid growth engines.
Example: Moving from paid acquisition to viral growth mechanics.
在病毒式、粘性或付费增长引擎之间切换增长策略。
示例： 从付费获取转向病毒式增长机制。

9. Channel Pivot

9. 渠道转型

Change the mechanism by which you deliver your product to customers.
Example: Moving from enterprise sales team to self-service online.
改变向客户交付产品的机制。
示例： 从企业销售团队转向自助式在线服务。

10. Technology Pivot

10. 技术转型

Achieve the same solution using completely different technology.
Example: Rewriting from scratch with new technology stack to improve performance.
使用完全不同的技术实现相同的解决方案。
示例： 使用新的技术栈重写代码以提升性能。

Pivot Process:

转型流程：

  1. Recognize: Data shows current approach isn't working
  2. Analyze: Review all validated learning to date
  3. Brainstorm: Generate pivot hypotheses
  4. Choose: Pick the most promising pivot based on data
  5. Plan: Design MVP to test new hypothesis
  6. Execute: Run through Build-Measure-Learn loop
  7. Evaluate: Did the pivot improve metrics?
Remember: Pivots are normal and expected. Most successful startups pivot at least once.
  1. 识别： 数据显示当前方法无效
  2. 分析： 回顾迄今为止的所有验证性学习内容
  3. 头脑风暴： 生成转型假设
  4. 选择： 根据数据选择最有前景的转型方向
  5. 规划： 设计MVP来测试新假设
  6. 执行： 完成Build-Measure-Learn循环
  7. 评估： 转型是否提升了指标？
记住： 转型是正常且预期之内的。大多数成功的创业公司至少转型过一次。

Three Engines of Growth

三大增长引擎

Every startup should focus on ONE engine of growth:
每个创业公司应专注于一种增长引擎：

1. Sticky Engine of Growth

1. 粘性增长引擎

Focus: Retention - keep customers coming back
Key Metrics:
  • Retention rate (% of customers who stay)
  • Churn rate (% of customers who leave)
  • Customer lifetime (how long average customer stays)
Growth Rule: Acquisition rate > Churn rate
Examples: SaaS products, subscription services, social networks
Optimization:
  • Improve onboarding
  • Add features that increase engagement
  • Build habits
  • Reduce churn
核心： 留存——让客户持续回头使用
关键指标：
  • 留存率（%的留存客户）
  • 流失率（%的流失客户）
  • 客户生命周期（平均客户留存时长）
增长规则： 获取率 > 流失率
示例： SaaS产品、订阅服务、社交网络
优化方向：
  • 改进用户引导
  • 添加提升参与度的功能
  • 培养使用习惯
  • 降低流失率

2. Viral Engine of Growth

2. 病毒式增长引擎

Focus: Referral - customers bring new customers
Key Metrics:
  • Viral coefficient (how many new customers does each customer bring?)
  • Viral cycle time (how long for one cycle of referral?)
Growth Rule: Viral coefficient > 1.0
Examples: Social networks, communication tools, marketplaces
Optimization:
  • Make sharing core to product experience
  • Incentivize referrals
  • Reduce friction in invite process
  • Speed up viral cycle time
核心： 推荐——客户带来新客户
关键指标：
  • 病毒系数（每个客户能带来多少新客户？）
  • 病毒循环时间（完成一次推荐循环需要多长时间？）
增长规则： 病毒系数 > 1.0
示例： 社交网络、通讯工具、市场平台
优化方向：
  • 让分享成为产品体验的核心
  • 激励推荐行为
  • 减少邀请流程的摩擦
  • 加快病毒循环时间

3. Paid Engine of Growth

3. 付费增长引擎

Focus: Acquisition - pay to acquire customers
Key Metrics:
  • Customer acquisition cost (CAC)
  • Lifetime value (LTV)
  • LTV:CAC ratio
Growth Rule: LTV > CAC (ideally LTV > 3x CAC)
Examples: Most B2B products, e-commerce
Optimization:
  • Increase LTV (upsell, reduce churn, raise prices)
  • Decrease CAC (improve conversion, optimize channels)
  • Improve monetization
Warning: Don't try to optimize multiple engines simultaneously. Pick one and master it.
核心： 获取——付费获取客户
关键指标：
  • 客户获取成本（CAC）
  • 生命周期价值（LTV）
  • LTV:CAC 比率
增长规则： LTV > CAC（理想情况下LTV > 3倍CAC）
示例： 大多数B2B产品、电商平台
优化方向：
  • 提升LTV（交叉销售、降低流失率、提价）
  • 降低CAC（提升转化率、优化渠道）
  • 改进变现方式
警告： 不要同时优化多个增长引擎。选择一个并精通它。

The Five Whys

五问法

A technique for getting to the root cause of problems by asking "why?" five times.
通过连续问五次“为什么？”来找出问题根源的技巧。

How to Use:

使用方法：

Problem: Website went down
  1. Why did website go down? Server ran out of memory
  2. Why did it run out of memory? Memory leak in new feature
  3. Why was there a memory leak? Code wasn't properly tested
  4. Why wasn't it tested? No automated tests for that component
  5. Why are there no automated tests? Team doesn't have time to write tests
Root cause: Need to invest in testing infrastructure
Solution: Allocate time for building automated tests
问题： 网站宕机了
  1. 为什么网站宕机？ 服务器内存不足
  2. 为什么内存不足？ 新功能存在内存泄漏
  3. 为什么会有内存泄漏？ 代码未经过适当测试
  4. 为什么未测试？ 该组件没有自动化测试
  5. 为什么没有自动化测试？ 团队没有时间编写测试
根本原因： 需要投入测试基础设施
解决方案： 分配时间构建自动化测试

Rules for Five Whys:

五问法规则：

  1. Be tolerant of all mistakes the first time
  2. Never allow the same mistake twice
  3. Start small - use for small problems first
  4. Appoint a Five Whys master to facilitate
  5. Everyone affected by problem must be in the room
  6. Make proportional investments - small problems = small fixes
  1. 第一次犯错时保持宽容
  2. 绝不允许重复犯同样的错误
  3. 从小处着手——先用于解决小问题
  4. 指定一位五问法负责人来主持
  5. 所有受问题影响的人必须到场
  6. 进行成比例的投入——小问题对应小修复

Lean Startup in Practice

Lean Startup 实践指南

Week-by-Week Framework:

每周实施框架：

Week 1: Hypothesis Definition

第1周：假设定义

  • Write down your riskiest assumptions
  • Prioritize which to test first
  • Design minimum experiment
  • Define success metrics
  • 写下你最具风险的假设
  • 确定优先测试的假设
  • 设计最小实验
  • 定义成功指标

Week 2-3: Build MVP

第2-3周：构建MVP

  • Build simplest version that tests hypothesis
  • Remember: embarrassingly simple is perfect
  • Focus on learning, not polish
  • 构建用于测试假设的最简版本
  • 记住：尴尬的简单才是完美的
  • 聚焦学习，而非打磨

Week 4: Measure

第4周：衡量

  • Get MVP in front of real customers
  • Collect actual usage data
  • Track defined metrics
  • Document customer feedback
  • 将MVP交付给真实客户
  • 收集实际使用数据
  • 跟踪既定指标
  • 记录客户反馈

Week 5: Learn

第5周：学习

  • Analyze results
  • What did you validate?
  • What did you invalidate?
  • What surprises emerged?
  • 分析结果
  • 你验证了什么？
  • 你推翻了什么？
  • 出现了哪些意外发现？

Week 6: Pivot or Persevere Decision

第6周：转型或坚持决策

  • Are metrics improving?
  • Did hypothesis prove true?
  • If yes: Persevere and tune the engine
  • If no: Pivot to new hypothesis
  • 指标是否有所提升？
  • 假设是否成立？
  • 如果是：坚持并优化引擎
  • 如果否：转型至新假设

Repeat: Faster and faster cycles

重复：持续加快循环速度

Common Lean Startup Mistakes

Lean Startup 常见误区

Mistake 1: Building Too Much

误区1：构建过多

Problem: Building full product before testing hypotheses. Fix: Start with simplest possible MVP. If you're not embarrassed, you waited too late.
问题： 在测试假设之前构建完整产品。 解决方法： 从最简MVP开始。如果你的第一个版本没有让你感到尴尬，说明你等待太久了。

Mistake 2: Analysis Paralysis

误区2：分析瘫痪

Problem: Spending months planning instead of testing. Fix: Get out of the building. Real customer data beats planning.
问题： 花费数月时间规划而非测试。 解决方法： 走出办公室。真实的客户数据胜过规划。

Mistake 3: Vanity Metrics

误区3：虚荣指标

Problem: Measuring things that don't help make decisions. Fix: Focus on actionable metrics that show cause and effect.
问题： 衡量无法帮助决策的内容。 解决方法： 聚焦能够体现因果关系的可行动指标。

Mistake 4: Ignoring the Data

误区4：忽视数据

Problem: Continuing with plan despite data showing it's not working. Fix: Be honest about what data is telling you. Pivot when needed.
问题： 尽管数据显示无效，仍坚持原有计划。 解决方法： 诚实地面对数据所传达的信息。必要时转型。

Mistake 5: Pivoting Too Fast

误区5：转型过快

Problem: Changing direction before giving approach enough iterations. Fix: Give each hypothesis multiple experiments before pivoting.
问题： 在给当前方法足够的迭代次数之前就改变方向。 解决方法： 在转型之前，为每个假设进行多次实验。

Mistake 6: Multiple Engines of Growth

误区6：多个增长引擎

Problem: Trying to optimize viral AND paid growth simultaneously. Fix: Pick one engine and master it before moving to another.
问题： 同时尝试优化病毒式和付费增长。 解决方法： 选择一个引擎并精通它，再考虑其他。

Mistake 7: No Clear Hypotheses

误区7：无明确假设

Problem: Building without clear assumptions to test. Fix: Write explicit hypotheses before every experiment.
问题： 在没有明确要测试的假设的情况下进行构建。 解决方法： 在每次实验前写下明确的假设。

Advice Framework

咨询框架

When providing Lean Startup advice:
提供Lean Startup建议时：

1. Understand Current State

1. 了解当前状态

Questions to ask:
  • What stage are you at?
  • What have you built so far?
  • What have you learned from customers?
  • What are you measuring?
  • What's your current Build-Measure-Learn cycle time?
需要询问的问题：
  • 你处于哪个阶段？
  • 你已经构建了什么？
  • 你从客户那里学到了什么？
  • 你正在衡量什么？
  • 你当前的Build-Measure-Learn循环时间是多少？

2. Identify the Problem

2. 识别问题

Common issues:
  • Building too much before testing
  • Not measuring the right things
  • Stuck in analysis paralysis
  • Pivoting too fast or too slow
  • Focusing on vanity metrics
常见问题：
  • 在测试之前构建过多
  • 没有衡量正确的内容
  • 陷入分析瘫痪
  • 转型过快或过慢
  • 聚焦虚荣指标

3. Apply Lean Principles

3. 应用Lean原则

Guide them toward:
  • Smaller MVPs
  • Faster cycles
  • Actionable metrics
  • Validated learning
  • Pivot or persevere decisions
引导他们走向：
  • 更小的MVP
  • 更快的循环
  • 可行动指标
  • 验证性学习
  • 转型或坚持决策

4. Provide Specific Actions

4. 提供具体行动

Format:
  • This week: [specific MVP to build]
  • Measure: [specific metrics to track]
  • Learn: [what question will you answer?]
  • Next week: [decision criteria for pivot/persevere]
格式：
  • 本周： [具体要构建的MVP]
  • 衡量： [要跟踪的具体指标]
  • 学习： [你将解答的问题]
  • 下周： [转型或坚持的决策标准]

5. Focus on Speed

5. 聚焦速度

Emphasize:
  • Minimize time through Build-Measure-Learn loop
  • Ship embarrassingly simple MVPs
  • Learn faster than competition
  • Don't optimize too early
强调：
  • 最小化Build-Measure-Learn循环的周期时间
  • 发布尴尬简单的MVP
  • 比竞争对手更快学习
  • 不要过早优化

Example Advice Session

咨询示例

Founder: "We're building an AI tool for content creators. We've been developing for 6 months and plan to launch in 3 more months with all features ready."
Lean Startup Response:
Assessment: You're in the "building too much before testing" trap. 9 months of building without customer validation is extremely risky.
Key Questions:
  • Have you talked to 50+ content creators about their problems?
  • Have any creators paid you or committed to pay?
  • What's your riskiest assumption?
  • Can you test that assumption this week instead of in 3 months?
Recommended Actions:
This Week:
  1. STOP building new features
  2. Create simplest MVP: One core feature only
  3. Get 10 content creators to use it (even if manual/ugly)
  4. Measure: Do they come back day 2? Day 7?
Metrics to Track:
  • Signup to activation rate
  • Day 1, 7, 30 retention
  • Customer willingness to pay
  • Core feature usage frequency
Learn:
  • Do creators have the problem you're solving?
  • Is your solution actually valuable to them?
  • What's the minimum feature set they need?
  • What will they pay?
Decision Point (Week 2):
  • If retention >40%: Persevere - keep building this approach
  • If retention <20%: Pivot - different problem or different customer
  • If willingness to pay low: Pivot monetization or value prop
Key Insight: You'll learn more in 2 weeks with a simple MVP than in 9 months of building in isolation. Speed up your learning loop.
创始人： "我们正在为内容创作者构建一款AI工具。我们已经开发了6个月，计划再用3个月完成所有功能后发布。"
Lean Startup 回复：
评估： 你陷入了“测试前构建过多”的陷阱。9个月的闭门开发而不进行客户验证风险极高。
关键问题：
  • 你是否与50多位内容创作者交流过他们的问题？
  • 有没有创作者已经付费或承诺付费？
  • 你最具风险的假设是什么？
  • 你能否在本周而非3个月后测试该假设？
建议行动：
本周：
  1. 停止开发新功能
  2. 创建最简MVP： 仅保留一个核心功能
  3. 让10位内容创作者使用它（即使是手动/简陋的版本）
  4. 衡量： 他们会在第2天、第7天回头使用吗？
跟踪指标：
  • 注册到激活的转化率
  • 第1、7、30天留存率
  • 客户付费意愿
  • 核心功能使用频率
学习：
  • 创作者是否存在你正在解决的问题？
  • 你的解决方案对他们是否真正有价值？
  • 他们需要的最小功能集是什么？
  • 他们愿意支付多少费用？
决策点（第2周）：
  • 如果留存率>40%： 坚持——继续推进此方向
  • 如果留存率<20%： 转型——解决不同问题或面向不同客户
  • 如果付费意愿低： 转型变现方式或价值主张
核心见解： 通过简单MVP，你在2周内学到的内容比9个月闭门开发学到的更多。加快你的学习循环。

Resources

参考资源

  • Book: "The Lean Startup" by Eric Ries
  • Book: "Running Lean" by Ash Maurya
  • Framework: Lean Canvas (1-page business plan)
  • Blog: startup-marketing.com
  • Principle: Build-Measure-Learn
  • Mantra: "Move fast and break things" → "Move fast and learn things"
  • 书籍： 《精益创业》（The Lean Startup）作者 Eric Ries
  • 书籍： 《Running Lean》作者 Ash Maurya
  • 框架： Lean Canvas（单页商业计划书）
  • 博客： startup-marketing.com
  • 原则： Build-Measure-Learn
  • 口号： “快速行动，打破常规” → “快速行动，持续学习”

Key Takeaways

核心要点

  1. Progress is learning, not building features
  2. Speed is more important than perfection
  3. Data beats opinions
  4. Small batches enable faster learning
  5. Actionable metrics drive decisions
  6. Pivot is normal, not failure
  7. MVP is about learning, not launching
  8. Focus on one engine of growth
  9. Validate before scaling
  10. Minimize cycle time through Build-Measure-Learn loop
"The lesson of the MVP is that any additional work beyond what was required to start learning is waste, no matter how important it might have seemed at the time." - Eric Ries
  1. 进展即学习，而非构建功能
  2. 速度比完美更重要
  3. 数据胜过观点
  4. 小批量实现更快学习
  5. 可行动指标驱动决策
  6. 转型是正常的，而非失败
  7. MVP的核心是学习，而非发布
  8. 聚焦一种增长引擎
  9. 先验证再规模化
  10. 最小化Build-Measure-Learn循环的周期时间
“MVP的经验是，任何超出启动学习所需的额外工作都是浪费，无论当时看起来多么重要。” - Eric Ries