The Essence of MVP in Product Development

There are many interpretation when talking about the definition of Minimum Viable Product (MVP). One of them, MVP is a product that has the most minimalist feature set, the goal is to prove the most essential hypothesis in the developed business. The forms also vary, although in a digital startup it will provide more experiences when it's an application, but it's possible to do something simpler.

The most frequently cited example is the MVP of Dropbox development, at that time it was only in the form of a video. A short video that lays out the gist of how the service they are going to develop works and the benefits it brings to users. Thousands, even hundreds of thousands of potential users signed up just by watching the video.

So the point of MVP is not on alpha/beta products from the application, but rather a way of giving consumers the opportunity to validate directly initial version of the product being developed. Because when the idea has been realized in something more real and published, people will more easily imagine it and determine whether the product is what they need or not.

Even MVP can be as simple as one single-webpage with an interesting explanation, then added an email field if there are interested visitors.

Be the most important stage, decide to continue or think of other ideas

In various discussions about "Lean Startup", MVP is always placed on the most important technique to do. According to Eric Ries, one who popularized the concept of MVP, that with the existence of an initiation product one can gather as much learning or feedback from consumers as possible.

Launching an MVP app is also said to be an art form. Because here requires the right precision between what you want to be served and what consumers really need. For this reason, before launching the MVP, it is necessary to know what components need to be considered, as the characteristics of the MVP.

There are at least three things that be the key in the development of MVP: (1) focuses on the essential usability of the product, so that when the product is actually launched, consumers are willing to use it; (2) provide consumers with an overview of the full functionality that will be presented in the future; and (3) provide a feedback channel to assist sustainable development.

Leads to measurable and realistic assessments, not assumptions

After MVP reaches consumers, there are many things to do. The simplest is to talk to consumers, to find out how they feel. The interesting thing is that now there are so many tools measurement that can be integrated, for example Google Analytics. From there will be found what is called the Problem-Solution Fit.

Problem-Solution Fit is simply when many users feel that what is born through the service answers their needs. But even when it reaches this is not enough. Because in the end all will be at stake for business purposes. Then, we need to think about Product-Market Fit, which is about how to achieve revenue of the business processes that have been developed.

From here what is obtained is the measurement. About what is most in demand from product initiation, what is most awaited, what input is given and so on. Everything must be clearly documented as a provision to ripen the product. Even to determine the termination of development if the proposed solution turns out to be ineffective.

Another thing to note, MVP must also be offered to the right market share. Marketed to people targeted as users. So that marketing efforts still play a key role at this stage.

Requires rigorous testing and focus on development

In addition to actively monitoring user feedback, testing is also necessary. There are many methodologies that can be used for product testing during the MVP period (this is more suitable when the MVP is an application or product that can be tried). One of the methodologies that can be used is A/B Split Test.

One of the things done by the testing methodology is to compare what the application produces when tested by changing the variables in the application. For example in button placement or menu functionality, make changes to some designs over a certain period of time. Then do the analysis, from the most immediate and common actions taken by the examiner. Even by potential customers though.

However, the focus on the main goal also needs attention. Often in the product development process, especially when you have launched an MVP, new ideas will emerge. It could be easy for someone to immediately pick up the idea and implement it into the product. Though not necessarily reliable and may add to the complexity of the product.

Whereas the simplicity of the process is very important in MVP to focus on the essence of the product. Impact of ideas-overflow if not managed properly is the failure of the MVP process in relation to consumer validation and market share.

There is a way to stay focused on the goals of initial product development

The first thing that needs to be done after having a specific idea about a product, the key to its development target. Lower the scope of the MVP (in terms of functionality and features) and then go into pre-production immediately. This is where the design process begins, but not without stumbling blocks. Usually it comes from the internal scope, namely the continuous development of ideas. Want to add this, add that and so on. What is needed here is not to get carried away easily. Focus on the original goal.

In the development process do it as quickly as possible. MVP doesn't need to be very full-featured, but it should definitely cover the main purpose of the idea. So do as little development as possible. Because it is necessary to present the product to consumers as soon as possible. Because the continued development or addition of features is the most appropriate when the input comes from consumers in general.

So it can be concluded, that MVP is basically an early stage validation in actual market share. If it is well validated, further development can rely on the input given, because it comes directly from potential users of the product in the future.