4 ms·
Indeed. Perhaps I misunderstood the general gist of Minimum Viable Product, but I thought it originated as a kind of test to determine whether what you had was
by jt2190 4y ago
Indeed.
Perhaps I misunderstood the general gist of Minimum Viable Product, but I thought it originated as a kind of test to determine whether what you had was actually a Product, and not just a one-off solution, or a piece of software, or some process that only a handful of people would ever actually pay for and use (hence the Viable part). Minimum was just guidance to not over-invest into any single part of the overall whole until all of the parts necessary for the Product were known. All of this would always be very specific to the particular Product.
Most people hear this advice and think it means they get to decide to cut corners, but what it actually means is that only your customers can tell you which corners they actually want; you never get to decide that for yourself.
- O__________O 4y agoTo me a MVP is designed largely to be the first step after speaking to customers to validate what they say versus what the do. After you see what they’re actually doing, then you talk to them again and repeat process where each future action attempts to increase odds of building a sustainable, preferably high-growth, business.
- jt2190 4y agoInteresting! It seems like you view MVP as the process whereas I view it as a milestone (something like the bare-minimum version of “default alive”.)