This comment will vaporize into the ether, but I have to say it anyway. Everyone needs to stop calling prototypes MVP's. The term MVP was coined by Frank Robi

This comment will vaporize into the ether, but I have to say it anyway. Everyone needs to stop calling prototypes MVP's. The term MVP was coined by Frank Robinson and popularized by Steve Blank. This term was unknown in product engineering 25 years ago, but the concepts were all there. Product development of software is not something new that was invented 5 years ago. People have been designing and building software products and systems for 50+ years, with all of the same issues and concerns of today's software products. All of them. The reason behind the development of the phrase "minimum viable product' was to help new entrepreneurial developers understand that the first release of a product to a limited set of customers should be designed to just meet the bare minimum yet valuable requirements of the customer. Repeat: the bare minimum yet valuable requirements. The MVP is not the first instantiation of a product. The term for that is a prototype. In product development, you build lots of prototypes, not just one. You build prototypes to test concepts and measure things. Sometimes you use a prototype to measure some customer interest and solidify a requirement; or maybe you identify new requirements or even eliminate requirements. As time goes on, these prototypes are pulled together and demonstrated as a whole functioning prototype. It is from this that a formal set of requirements and a formal product design is solidified--for your MVP. The functional and demonstrable prototype is most likely not hour MVP. Why? Because in the development of the prototype you probably didn't worry much about things like UI/UX, customer support, lowest cost for product delivery, robustness, bandwidth usage, supportability, testability, ability to measure usage, and the list goes on. It's okay that you didn't care about these things yet, because you were just trying to prove the concept, to get something working, and/or to gauge people's interest. But now, you have to build a PRODUCT: something valuable and of very good quality with excellent support that you can sell thousands of times. What is the minimum VIABLE product that you can start selling to your customers that has the best chance of succeeding without screwing up the whole opportunity and losing all of the work you have done so far? Something that will tell you if you have identified the sweet spot, or if you need to adjust the value to increase the number of customers. THAT is the MVP. If you don't believe me, just go back and read the origin of the phrase on the Wayback Machine: http://www.syncdev.com/minimum-viable-product/ http://www.syncdev.com/minimum-viable-product/ Or read this article on the difference between prototypes and MVP's: https://productschool.com/blog/product-management-2/difference-prototype-mvp/ https://productschool.com/blog/product-management-2/differen... Good luck to all of the new product developers.