The Lean Startup — One-Page Summary

Name: The Lean Startup
ISBN: 9780307887894

(subtitle: by Eric Ries)

Why it matters (1–2 lines)

Build products people actually want, faster and with less waste. Turn uncertainty into a repeatable system for learning, growth, and better decisions.

Big ideas (8–10 bullets)

Start with leap-of-faith — Identify the riskiest assumptions (value and growth) first, so you test what can kill your idea before you spend months polishing nonessentials.
MVPs test hypotheses — Build the smallest experiment that can prove or disprove a key assumption, so you get real feedback from real customers without overbuilding.
Build–Measure–Learn fast — Ship something, measure what customers do, and learn whether to change or continue; shorter cycles mean more shots on goal and faster progress.
Actionable metrics over vanity — Use cohort analysis, split tests, and cause-and-effect metrics, so you steer by what changes behavior, not by feel-good totals or aggregates.
Innovation accounting guides progress — Establish a baseline with an MVP, tune the engine to improve a few key metrics, then decide to pivot or persevere; this defines progress when revenue and scale are not yet reliable.
Pivot or persevere deliberately — Schedule a recurring decision point to review evidence against your hypotheses, so you avoid slow death by incrementalism or stubbornness.
Small batches, continuous deployment — Work in tiny chunks and ship often, so you reduce risk, find defects sooner, and keep learning flowing through the team.
Engines of growth focus — Choose a primary growth engine (sticky via retention, viral via sharing, or paid via CAC/LTV), so you optimize one system at a time and avoid muddled targets.
Five Whys for learning — When problems hit, ask “why” five times and fix root causes with proportional investment, so quality and speed improve together over time.
Entrepreneurship is management — Treat startups (including new ventures inside big firms) as a management problem under uncertainty, so you design culture, process, and metrics for learning, not for static plans.

What most readers miss (3–5 bullets)

MVP is about learning — It is not permission to ship junk; it must make a clear hypothesis and include a way to measure whether the hypothesis is true.
Speed needs discipline — Going faster only helps if experiments are falsifiable, metrics are trustworthy, and deployment/analytics are automated; otherwise you accelerate chaos.
Pivots keep vision, change path — A pivot is a strategy shift grounded in evidence, not a total reset; you preserve the vision while changing how you pursue it.
Pick a primary growth engine — You can use multiple channels, but declare one as the main engine and judge it with the right metric (e.g., churn for sticky, viral coefficient for viral), or you’ll hide signal in noise.
Learning requires hard thresholds — Innovation accounting works only if you set explicit metric targets in advance; without thresholds, rationalization creeps in and you never pivot.

Three practical takeaways

When scoping your next feature or campaign, do write a single-sentence, falsifiable hypothesis with a success metric and build the smallest MVP to test it within two weeks, because faster validated learning beats building on assumptions.
When reviewing growth, do switch to cohort-based metrics and run at least one A/B test that targets your primary engine of growth each sprint, because you need causal evidence to know what to scale or cut.
When defects or delays recur, do run a Five Whys with the whole team and add one proportional process fix (e.g., a test, checklist, or automation) to your definition of done, because systematic improvements prevent repeat waste.

If you only remember one thing (1 line)

Optimize for learning per unit time: run the Build–Measure–Learn loop on your riskiest assumptions until evidence tells you to pivot or persevere.

The Lean Startup