The Lean Startup: Why Learning Beats Launching

Eric Ries wrote The Lean Startup after watching his own early venture burn through years of work on a product customers did not want. The book borrows from lean manufacturing and turns it into a method for building anything under uncertainty. It reaches well beyond tech companies.

Here are six ideas worth keeping.

1. A startup is an experiment, not a smaller company. Ries defines a startup as a human institution designed to create something new under conditions of extreme uncertainty. If you are not sure what customers want, a detailed plan gives you false confidence, not progress.

2. Progress means validated learning. Features shipped and hours worked are not progress. Evidence about what customers actually value is. Every step should answer a real question about your business.

3. Build the minimum viable product. The MVP is the smallest version that lets you start learning. Ries tells of Dropbox, which tested demand with a short demo video before the full product existed. The goal is the answer, not the polish.

4. Run the build-measure-learn loop, and make it fast. Turn an idea into a product, measure how people respond, then learn from it. The team that completes more loops per month learns faster than the team with the better first guess.

5. Measure what matters, not what flatters. Ries calls total sign-ups and page views vanity metrics: they rise even when the business is not working. He favors actionable ones, such as the share of new users who come back, tracked cohort by cohort.

6. Know when to pivot. A pivot is a structured change of direction that keeps what you have learned. If repeated experiments show the numbers are not moving, the honest move is to change the strategy, not push harder on the same one.

The book's quiet point is about humility. Building is easy to confuse with learning, and a plan is easy to confuse with evidence. Ries asks you to find out sooner, while being wrong is still cheap.