3 ms·
I think this is a bit of a misread of what MVP means. It's not a prototype or a way to search for the right product to build. It's prioritising the minimum set
by robertlagrant 5y ago
I think this is a bit of a misread of what MVP means. It's not a prototype or a way to search for the right product to build. It's prioritising the minimum set of features to launch a viable product.
That pretty obviously implies that you already know what to build, at least roughly, so that thinking has been done. If you need more than 20 objects and pagination, then that's part of the V in MVP.
The difference is that you don't spend 2 years on 100 features you think people will want (or even, people tell you they want) - you boil that research down to 15 features that can work together as a product that you've defined will be useful, and then build the next set of features on top that will allow you to access more of the market, partly based on what you learned from the previous iteration, etc etc.
You may still spend 2 years building (and you should definitely carve out budget assuming that) and you may still build 100 features, but you launched much earlier to get information, and you may have built 30 features differently due to the extra information you got, and you'll have got a pretty battle-tested product into the market by the end of the two years.
You probably know all this. I'm restating because I read so many articles that confuse an idea with observed (or anecdotal) bad implementations, and this seems to do the same thing.