Reactify Solutions

The Lean Startup, explained

What counts as a startup, why most of the work in one is waste, and the loop that replaces guessing with evidence.

Product teams and foundersLast reviewed September 5, 2026
In one minute
  • A startup is any team building something new under real uncertainty. Company size does not matter.
  • The waste is not slow coding. It is building the wrong thing beautifully.
  • The fix is a loop: build a small thing, measure what happens, learn, then decide whether to keep going or change direction.
  • Progress is measured in learning, not in features shipped.

What counts as a startup

Ries defines it broadly: a human institution built to create something new under conditions of extreme uncertainty. A two-person app and a new product line inside an eighty-year-old bank both qualify. What matters is the uncertainty, not the funding or the office.

The waste this targets

Most startup effort goes into building things nobody wants. The code works, the deadline is met, the feature ships, and it changes nothing.

Traditional planning cannot catch this, because a plan assumes you already know the customer and the problem. Under real uncertainty you do not. So the plan produces confident, detailed, wrong work.

The loop

Execute forwards, plan backwards
1Build
An MVP
The smallest thing that tests the idea
2Measure
Data
Split tests and cohorts, not totals
3Learn
A decision
Pivot, or keep going
What you learn feeds the next build. Each pass ends with a decision, not a release.
Plan in reverse · decide what you need to learn, work out what to measure to learn it, then build only enough to get that measurement.
The goal · shorten total time through the loop. That is the number to improve, not the speed of any one step.

The loop is the whole method. Everything else in this handbook is a tool for running it faster or reading its output honestly.

Two things people get wrong about it:

  1. You plan it backwards. Running it forwards from "what should we build" is how you end up with a feature and no answer.
  2. Speed means the whole loop. A team that ships in a day and takes four months to read the result is slow.

What this handbook covers

SectionWhat it answers
The five principlesWhy this works, and who it is for
Build, measure, learnHow to run one cycle
The MVPThe smallest thing that answers the question
Metrics that are not liesVanity numbers, the three A's, split tests
Innovation accountingHow to show progress before you have revenue
Pivot or persevereThe meeting, and the ten kinds of pivot
Engines of growthSticky, viral, paid, and which one you are running
Finding root causesFive whys, and when to use a fishbone instead
Inside an existing companyRunning this where there is already a business to protect
The one sentence version

Stop asking "can we build this?" Almost anything can be built. Ask "should we build this, and will anyone use it?", then go find out cheaply.

Last reviewed September 5, 2026 · verified against The Lean Startup, Eric Ries, 2011