MVP, PROTOTYPE, POC сравнение, назначение

Before starting an idea, many people have different names for the intended result. The most common terms in this case are: MVP (minimum viable product), POC (proof-of-concept), Prototype.

Let's try to figure out in which cases it is most appropriate to use each of the above definitions in order to avoid misunderstanding

MVP

Minimum viable product is a version of a product that has a minimum set of functions solely for the realization of a business goal, while maintaining viability. In other words, it does not contain a bunch of interesting “features” and a beautiful interface. It makes sense to use such a solution when working with startups in order to bring the product to the market and find out whether it will be in general demand. Thus, if demand has appeared, then there is a sense of further work and you can try to get money from the first investors to develop the product in the future. Naturally, in the light of the fact that MVP is sent directly to the market, it should be a stable version of software that works without errors.

POC

The so-called proof of concept. Unlike MVP, this is a small project designed to test critical hypotheses before starting a full-fledged development. For example, POC is created in order to check whether it is possible to implement any function at all or, if there is no certainty that the idea will work. Confirmation of the concept does not cover the entire system, but only a small part of it, which users may not even see at all, because most often POCs are used internally to clarify the product development path. Roughly speaking, POC is a small study that gives green (or red) light for further work, whether it is the beginning of a new project or the development of an existing one. There are times when POC is used instead of MVP to obtain financing.

Prototype

And the last, but no less important definition in our review is the prototype. The main goal of creating a prototype is to help make a decision on product development and reduce the number of errors in it. A prototype is a working model of several aspects of a product (unlike POC, where one function is more often implemented). Most often, prototyping is used to demonstrate any part of the system, detect errors in it, and survey users. Using a prototype, the team checks the product design, usability, and often functionality, which you can’t do with POC. Simply put, the prototype is more like a draft - i.e. a kind of rough draft, which still requires a lot of improvements, but it is shown to end users in order to hear their opinion in general about the result. It is important to note,that prototypes are often used to implement some fresh ideas, and subsequently may well develop into MVP.

Summing up to the above, I propose, for clarity, to compare the described terms in a small table:

In the end, I want to note that although MVP, POC and Prototype have much in common, but still they have different goals. And also that in the course of work POC can develop into a prototype or MVP or vice versa. As a result, it is up to you to decide which path to take.

In our work with startups, we most often dealt with MVP, which could be preceded by POC and / or Prototype.