Explain the MVP (per Eric Ries) as a tool for cheap learning that tests the key value hypothesis, not as a merely 'stripped-down product'.
MVP: a learning tool, not a 'stripped-down product'
MVP: a learning tool, not a 'stripped-down product'
Per Eric Ries (the book 'The Lean Startup'), an MVP is the version of a new product that lets you collect the maximum amount of validated learning with the least effort. The key word here is 'learning', not 'product'. The goal of an MVP is to answer the riskiest question about value — 'Do people actually need this?' — before pouring large resources into development.
Many teams confuse an MVP with 'a small but working product' and start building a trimmed-down version of every planned feature. That is a trap: this approach still takes months of development and, more importantly, does not answer the key question about value. A real MVP is not about what you will build; it is about what you will learn.
An MVP starts the Build–Measure–Learn loop: you build a minimal experiment, measure how users react, draw a conclusion, and then either stay the course (persevere) or change direction (pivot). The faster you go around this loop, the less you spend on wrong hypotheses.
Example: a startup wants to learn whether people will pay for organic grocery delivery. Instead of building a platform, they create a simple landing page with a 'Subscribe' button and run some ads. If 5% of visitors click the button, the demand hypothesis is supported. That is an MVP: cheap, fast, and it gives a clear answer to the main question.
Lesson notes
MVP: a learning tool, not a 'stripped-down product'
Per Eric Ries (the book 'The Lean Startup'), an MVP is the version of a new product that lets you collect the maximum amount of validated learning with the least effort. The key word here is 'learning', not 'product'. The goal of an MVP is to answer the riskiest question about value — 'Do people actually need this?' — before pouring large resources into development.
Many teams confuse an MVP with 'a small but working product' and start building a trimmed-down version of every planned feature. That is a trap: this approach still takes months of development and, more importantly, does not answer the key question about value. A real MVP is not about what you will build; it is about what you will learn.
An MVP starts the Build–Measure–Learn loop: you build a minimal experiment, measure how users react, draw a conclusion, and then either stay the course (persevere) or change direction (pivot). The faster you go around this loop, the less you spend on wrong hypotheses.
Example: a startup wants to learn whether people will pay for organic grocery delivery. Instead of building a platform, they create a simple landing page with a 'Subscribe' button and run some ads. If 5% of visitors click the button, the demand hypothesis is supported. That is an MVP: cheap, fast, and it gives a clear answer to the main question.