Minimum viable product

A minimum viable product (MVP) is a version of a product with just enough features to satisfy early customers and provide feedback for future product development.[1][2]

Gathering insights from an MVP is often less expensive than developing a product with more features, which increases costs and risk if the product fails, for example, due to incorrect assumptions.[3] The term was coined and defined in 2001 by Frank Robinson[4] and then popularized by Steve Blank and Eric Ries.[5][6][7][8] It may also involve carrying out market analysis beforehand.


A minimum viable product has just enough core features to effectively deploy the product, and no more. Developers typically deploy the product to a subset of possible customers—such as early adopters thought to be more forgiving, more likely to give feedback, and able to grasp a product vision from an early prototype or marketing information. This strategy targets avoiding building products that customers do not want and seeks to maximize information about the customer with the least money spent.

"The minimum viable product is that version of a new product a team uses to collect the maximum amount of validated learning about customers with the least effort."[2] The definition's use of the words maximum and minimum means it is not formulaic. It requires judgement to figure out, for any given context, what MVP makes sense. Due to this vagueness, the term MVP is commonly used, either deliberately or unwittingly, to refer to a much broader notion ranging from a rather prototype-like product to a fully-fledged and marketable product.[9]

An MVP can be part of a strategy and process directed toward making and selling a product to customers.[10] It is a core artifact in an iterative process of idea generation, prototyping, presentation, data collection, analysis and learning. One seeks to minimize the total time spent on an iteration. The process is iterated until a desirable product/market fit is obtained, or until the product is deemed non-viable.

Steve Blank typically refers to minimum viable product as minimum feature set.[11][12]


  • Be able to test a product hypothesis with minimal resources
  • Accelerate learning
  • Reduce wasted engineering hours
  • Get the product to early customers as soon as possible
  • Base for other products
  • To establish a builder's abilities in crafting the product required
  • Brand building very quickly

Key MVP elementsEdit

An MVP must include these key elements in production quality:[13]

  • Functionality - the set of features must deliver clear value to the user,
  • Design - the design of the MVP must be up to the highest industry standard,
  • Reliability - production quality standard needs to be achieved by rigorous testing,
  • Usability - the MVP must be easy to use and intuitive,


  • Results from a minimum viable product test aim to indicate if the product should be built to begin with. Testing evaluates if the initial problem or goal is solved in a manner that makes it reasonable to move forward.

Notable quotesEdit

  • Steve Blank: "You’re selling the vision and delivering the minimum feature set to visionaries, not everyone."[11]


Releasing and assessing the impact of a minimum viable product is a market testing strategy that is used to screen product ideas soon after their generation. In software development, the release is facilitated by rapid application development tools and languages common to web application development.

The whole point of MVP is to make quick working project or ready business, cause the average time of development is 1,5 month[14]. Using MVP companies can build more accurate market predictions and attract new investments.

The MVP differs from the conventional market testing strategy of investing time and money early to implement a product before testing it in the market. The MVP is intended to ensure that the market wants the product before large time and monetary investments are made. The MVP differs from the open source software methodology of release early, release often that listens to users, letting them define the features and future of the product. The MVP starts with a product vision, which is maintained throughout the product life cycle, although it is adapted based on the explicit and implicit (indirect measures) feedback from potential future customers of the product.[2]

The MVP is a strategy that may be used as a part of Blank's customer development methodology that focuses on continual product iteration and refinement based on customer feedback. Additionally, the presentation of non-existing products and features may be refined using web-based statistical hypothesis testing, such as A/B testing.

Business Model CanvasEdit

The Business Model Canvas is used to map in the major components and activities for a company starting out. The minimum viable product can be designed by using selected components of the Business Model Canvas:[15]

  • Customers
  • Value proposition
  • Channels
  • Relationship

Emerging applicationsEdit

Concepts from minimum viable product are applied in other aspects of startups and organizations.

Minimum viable brand (MVB)Edit

Using a minimum viable brand (MVB) concept can ensure brand hypotheses are grounded in strategic intent and market insights.[16]

Minimum viable co-founderEdit

Finding other people to create a minimum viable product is a common challenge for new companies and startups. The concept of minimum viable co-founder is based on looking for a co-founder with the following attributes:[17]

  • Trust
  • Exceptional at building or selling
  • Company commitment
  • Personally likeable
  • Productivity
  • Reasonable
  • Rational
  • Realistic

Minimum viable teamEdit

Founders with an early-stage company are faced with the challenge of building a team with minimal people and cost. The process starts by listing out basic functions of a particular company (e.g., engineer, operations, finance) and then stripping down to the abstract job activities and skills that the company must have to operate.[18][19]


Some research has showed that early release of an MVP may hurt a company more than help when companies risk imitation by a competitor and have not established other barriers to imitation.[20] It has also indicated that negative feedback on an MVP can negatively affect a company's reputation.[20] Many developers of mobile and digital products are now criticizing the MVP because customers can easily switch between competing products through platforms (e.g. app stores).[21] Also, products that do not offer the expected minimum standard of quality are inferior to competitors that enter the market with a higher standard.

The criticism of the MVP approach has led to several new approaches, e.g. the Minimum Viable Experiment MVE,[22] the Minimum Awesome Product MAP,[23] or the Simple, Lovable, Complete.[24]

See alsoEdit


  1. ^ "What is a Minimum Viable Product (MVP)? - Definition from Techopedia".
  2. ^ a b c Ries, Eric (August 3, 2009). "Minimum Viable Product: a guide".
  3. ^ "MVP: A maximally misunderstood idea". Slalom. Retrieved 2019-12-04.
  4. ^ "SyncDev methodology". SyncDev. Retrieved May 16, 2016.
  5. ^ W. S. Junk, "The Dynamic Balance Between Cost, Schedule, Features, and Quality in Software Development Projects", Computer Science Dept., University of Idaho, SEPM-001, April 2000.
  6. ^ Eric Ries, March 23, 2009, Venture Hacks interview: "What is the minimum viable product?", Lessons Learned
  7. ^ Perfection By Subtraction – The Minimum Feature Set
  8. ^ Holiday, Ryan The single worst marketing decision you can make The Next Web. 1 April 2015
  9. ^ Ambler, Scott (2017-12-27). "Defining MVP, MMF, MMP, and MMR". The Disciplined Agile (DA) Framework. Retrieved 23 August 2018.
  10. ^ Radoff, Jon (May 4, 2010). "Minimum Viable Product rant". Jon Radoff's Internet Wonderland. Archived from the original on March 23, 2014. Retrieved 19 August 2014.CS1 maint: unfit url (link)
  11. ^ a b Blank, Steve (March 4, 2010). "Perfection By Subtraction – The Minimum Feature Set".
  12. ^ Lenarduzzi, Valentina; Taibi, Davide (August 2016). MVP Explained: A Systematic Mapping Study on the Definitions of Minimal Viable Product. 2016 42nd Euromicro Conference on Software Engineering and Advanced Applications (SEAA). Cyprus. pp. 112–119. doi:10.1109/SEAA.2016.56.
  13. ^ "MVP - what is it and why is it crucial for your business?". Pixelfield blog. 2020-01-06. Retrieved 2020-01-07.
  14. ^ 1,5 MVP [1]
  15. ^ Kromer, Tristan (April 15, 2014). "The Four Parts of a Minimal Viable Product". Archived from the original on July 22, 2015. Retrieved April 25, 2014.
  16. ^ "Start-Ups Need a Minimum Viable Brand". Harvard Business Review. Retrieved 2017-09-20.
  17. ^ Shah, Darmesh (October 5, 2011). "Choosing A Minimally Viable Co-Founder".
  18. ^ Kromer, Tristan (October 11, 2011). "A Minimum Viable Team is More Important than a Minimum Viable Product".
  19. ^ O'Donnell, Charlie (August 22, 2012). "Minimum Viable Team".
  20. ^ a b "The Limitations of Lean Startup Principles". Knowledge@Wharton, Wharton School of the University of Pennsylvania. 28 September 2018. Retrieved 17 October 2018.
  21. ^ Beneyto, Carlos (February 5, 2018). "The MVP is dead, long life to the MAP. (Minimum Awesome Product)".
  22. ^ "Death to the Minimum Viable Product! | Lean User Testing". January 11, 2019.
  23. ^ fluidmobile GmbH (January 22, 2019). "Minimum Awesome Product in der App-Entwicklung".
  24. ^ Cohen, Jason (22 Aug 2017). "I hate MVPs. So do your customers. Make it SLC instead".