A good question to ask is: what is someone going to stop doing when they start using your product?
Source: https://cheesecakelabs.com/blog/product-validation-building-app/
An MVP is a process that you repeat over and over again: Identify your riskiest assumption, find the smallest possible experiment to test that assumption, and use the results of the experiment to course correct.
When you build a product, you make many assumptions.
The only way to find that out—the only way to test your assumptions—is to put your product in front of real users as quickly as possible. And when you do, you will often find that you have to go back to the drawing board.
Let’s try the MVP-as-a-process approach and see if we can do better. We will build the product incrementally, at each stage asking:
- What is my riskiest assumption?
- What is the smallest experiment I can do to test this assumption?
Source: https://www.ycombinator.com/blog/minimum-viable-product-process/
There is a flaw at the heart of the term Minimum Viable Product: it’s not a product. It’s a way of testing whether you’ve found a problem worth solving. A way to reduce risk and quickly test your biggest assumption.
MVP is used so much it’s lost its original meaning. It’s often mistakenly applied to the first release of a rudimentary product. As a result, the “MVP” ends up much more complex than the quick test it was supposed to be and far too shoddy for a released product.
What’s the smallest experiment you can do to test your biggest assumption?
Maximising the rate of learning by minimising the time to try things.
Source: https://hackernoon.com/the-mvp-is-dead-long-live-the-rat-233d5d16ab02