A minimum viable product (MVP) is a concept from Lean Startup that stresses the impact of learning in new product development. Eric Ries, defined an MVP as that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. This validated learning comes in the form of whether your customers will actually purchase your product.
A key premise behind the idea of MVP is that you produce an actual product (which may be no more than a Landing Page, or a service with an appearance of automation, but which is fully manual behind the scenes) that you can offer to customers and observe their actual behavior with the product or service. Seeing what people actually do with respect to a product is much more reliable than asking people what they would do.
The primary benefit of an MVP is you can gain understanding about your customers’ interest in your product without fully developing the product. The sooner you can find out whether your product will appeal to customers, the LESS effort and expense you spend on a product that will not succeed in the market.
Teams use the term MVP, but don’t fully understand its intended use or meaning. Often this lack of understanding manifests in believing that an MVP is the smallest amount of functionality they can deliver, without the additional criteria of being sufficient to learn about the business viability of the product.
Teams may also confuse an MVP–which has a focus on learning–for a Minimum Marketable Feature (MMF) or Minimum Marketable Product (MMP)–which has a focus on earning. There’s not too much harm in this unless the team becomes too focused on delivering something without considering whether it is the right something that satisfies customer’s needs.
Teams stress the minimum part of MVP to the exclusion of the viable part. The product delivered is not sufficient quality to provide an accurate assessment of whether customers will use the product.
Teams deliver what they consider an MVP, and then do not do any further changes to that product, regardless of feedback they receive about it.
Proper use of an MVP means that a team may dramatically change a product that they deliver to their customers or abandon the product together based on feedback they receive from their customers. The minimum aspect of MVP encourages teams to do the least amount of work possible to useful feedback (Eric Ries refers to this as validated learning) which helps them avoid working on a product that no one wants.
2009: The concept of MVP gained popularity after Eric Ries described it in his book the Lean Startup
Signs of Use
A team effectively uses MVP as the core piece of a strategy of experimentation. They hypothesize that their customers have a need and that the product the team is working on satisfies that need. The team then delivers something to those customers in order to find out if in fact the customers will use the product to satisfy those needs. Based on the information gained from this experiment, the team continues, changes, or cancels work on the product.