The Lean Startup

Review

I read The Lean Startup in 2017, a few years after it had already become foundational reading in product circles. It still held up. Ries identified something that should be obvious but apparently was not: most of what startups build is waste, because teams build before confirming a customer actually wants the thing. The build-measure-learn loop is the antidote, not because it's clever, but because it forces you to confront assumptions while they are still cheap to test.

What I respect most is that the book doesn't just hand you a philosophy. It gives you working frameworks: innovation accounting, pivot vs persevere, the three engines of growth. These have aged well. My honest caveat is that the second half over-explains. Ries makes the core argument in the first third, then spends the remaining pages reinforcing it with case studies. You don't need all of them.

Read the first half carefully. It's among the most important books written about product work.

Key Takeaways

The parts worth keeping

The core problem

• Startups produce a lot of waste, primarily products customers don't want.
• Entrepreneurship is management of extreme uncertainty.
• Tools of general management don't do well under extreme uncertainty.
• The goal: figure out the right thing to build as quickly as possible.
• It doesn't matter if you're on time, on budget, and doing quality work if you're building something nobody wants.

Validated learning

• Learning is the essential unit of progress for startups.
• Validated learning is a rigorous method for demonstrating progress in extreme uncertainty.
• Systematically break down a business plan into its component parts and test each one empirically.
• Two key hypotheses every entrepreneur should test:
  • Value hypothesis: does the product deliver real value to customers once they are using it?
  • Growth hypothesis: how will new customers discover the product?
• Four questions to answer before building:
  • Do customers recognize they have the problem you're trying to solve?
  • If a solution existed, would they buy it?
  • Would they buy it from us?
  • Can we build a solution to that problem?
• If you can't fail, you can't learn.
• Success isn't delivering a feature. Success is learning how to solve the customer's problem.

Build-measure-learn

• A startup transforms ideas into products. As customers interact with those products, they generate feedback and data.
• Ideas → Build → Product → Measure → Data → Learn → repeat
• The goal is to minimize total time through the feedback loop.
• Information is the most important currency in uncertain environments.

Minimum viable product

• An MVP helps entrepreneurs start the process of learning as quickly as possible.
  • It's not the smallest possible product.
  • It's the fastest way to get through the build-measure-learn feedback loop.
• The MVP rule: remove any feature, process, or effort that doesn't contribute directly to the learning you seek.
• An MVP tests viability, usability, and feasibility.
• Early adopters are fine with an 80% product. They feel the problem most acutely.
• Customers don't care how long something took to build. They care that it serves their needs.
• MVPs can take many forms: teaser videos, concierge, wizard of oz.

Innovation accounting

• Innovation accounting is a new type of accounting designed for disruptive innovation. It gives you a way to prove you're learning to grow a sustainable business.
• Step 0: Turn your leap-of-faith assumptions into a quantitative financial model.
• Step 1: Establish a baseline. Use an MVP to collect real data on where the company is right now. This is the first learning milestone.
• Step 2: Tune the engine. Make changes to move results toward the ideal.
• Step 3: Pivot or persevere. Assess how quickly you're closing the gap. If you're not making progress fast enough, the strategy may be flawed and a pivot is worth considering. If you pivot, check whether the fundamentals are improving faster than before.

Pivot or persevere

• Think of your startup's runway as the number of pivots you can make, not months of cash remaining.
• Founders consistently say they wish they had pivoted sooner.
• Have a regular pivot-or-persevere meeting. Find your own cadence.
• Actionable metrics vs vanity metrics:
  • Vanity metrics amplify attribution bias: when results go up, we assume it's because of what we did.
  • Cohort metrics beat gross metrics. Split tests beat ubiquitous changes.
  • Metrics should be actionable, auditable, and accessible.

Engines of growth

• Engine of growth: the mechanism a startup uses to achieve sustainable growth.
• Sustainable growth means new customers come from the actions of past customers: word of mouth, side effects of product usage, funded advertising, or repeat purchase.

• Every engine of growth will eventually run out of gas.
• Evaluate how close you're to product/market fit by reviewing and tuning your growth engine. If you're asking whether you have achieved it, you probably have not.

Quality and the 5 Whys

• Shortcuts in quality, design, or infrastructure today slow you down tomorrow.
• The 5 Whys technique: ask why five times to move from a technical fault to the human cause underneath it.
• Make proportional investments at each level. Small problems get small fixes. Large problems warrant larger ones.
• Culture: be tolerant of all mistakes the first time. Never allow the same mistake twice.