What is the Lean Startup method?
Many startups fail not because the idea is bad but because nobody checked it. The Lean Startup method (popular from the writer Eric Ries) says: treat your idea as a hypothesis, a guess, and test it quickly with real customers using as little money as possible.
Instead of one long plan, you run short experiments and learn from the results. "Lean" means no waste: do not build what nobody wants.
Customer development
Customer development (idea from Steve Blank) means "get out of the building": talk to real customers before and while you build. Four short steps:
- Discover: find out the real problem of customers.
- Validate: check if enough customers would really pay for your solution.
- Create: build demand and attract more customers.
- Build: grow the company once the model works.
Ask about their life and their problem, not "do you like my idea?". What people do (paying, coming back) is stronger proof than what they say.
MVP and the build-measure-learn loop
An MVP (Minimum Viable Product) is the smallest version of your product that lets real customers try the main idea. It may be a simple web page, a hand-made sample, or a short video. It is not a bad product; it is a focused test.
The build-measure-learn loop:
- Build the MVP.
- Measure what customers really do: sign-ups, orders, repeat use, money paid.
- Learn if the guess was right or wrong.
Then repeat. The faster you go around the loop, the cheaper your mistakes are.
Pivot or persevere
After learning, the founder decides.
- Persevere: the numbers reach your target, so keep the plan and improve it.
- Pivot: the numbers miss the target, so keep what you learned but change one big part: the customer group, the product, the price or the way you earn money.
A pivot is not a failure. It is a smart change of direction based on facts. Decide the target before the test (for example: at least 4 of 10 customers pay), so you are not fooled by hope.
Agile product development
Agile product development builds the product in short rounds called sprints, usually 1 to 4 weeks. At the end of each sprint the team shows a small working part to customers and collects feedback. The next sprint plan changes with that feedback.
Compare the old "waterfall" way: plan everything, build for a year, show the customer at the end. If the plan was wrong, the whole year is lost. Agile and Lean Startup fit well together: Lean decides what to build, agile decides how to build it in small steps.
Try it: test an idea this weekend
Choose a small idea, such as selling homemade snacks to your building. Write your guess in one line and your target (for example: 4 of 10 neighbours order). Make an MVP: a handwritten menu and one order message. Ask 10 people, count the orders, then decide to persevere or pivot. In the 3D, use the slider to see what your result would mean.
Key formulas and definitions
- Build → Measure → Learn → (repeat)
- MVP = Minimum Viable Product
- Decision: result ≥ target → persevere; result < target → pivot
- Success rate % = customers who said yes ÷ customers asked × 100
- Releases per year (agile) = weeks in year ÷ weeks per sprint
Worked examples
1. A founder asks 20 customers and 6 say they would pay. What is the success rate?
6 ÷ 20 × 100 = 30%.
2. The goal was "at least 40% say yes". The result above is 30%. Pivot or persevere?
30% is below 40%, so the goal is missed. The founder should pivot: keep the lessons but change one big part (customer, product or price).
3. Which is the MVP for an idea of a home-tutor app: a full app with payments or a simple form where parents request a tutor?
The simple form. It tests the main idea (do parents want this?) in days. The full app can be built later if demand is real.
4. A team works in 2-week sprints. How many releases can it make in one year (52 weeks)?
52 ÷ 2 = 26 releases, so customers can give feedback 26 times a year.
5. Why is "12 customers paid ₹50 advance" stronger evidence than "20 customers said they like it"?
Paying is real behaviour with a cost to the customer. Saying "I like it" costs nothing, so it can be polite and untrue.
Common mistakes
- Building the full product first and meeting customers last. In Lean Startup you meet customers first.
- Thinking an MVP means a poor-quality product. It is the smallest version that tests the main idea well.
- Trusting what customers say instead of what they do (pay, return, recommend).
- Treating a pivot as a failure, or changing direction without a clear target and data.