MVP

In the build face the goal is to produce a minimum viable product. 

The MVP could be defined as the minimum set of functionalities that needs an entrepreneur to learn from his clients, specifically in those who are interested in his product (it means those who suffer they need, and the product is being designed to solve or fulfill it) so this target will be more involved in the using of the product and talk about it.

“MVP” is a partial version of a product guided to discover in quick way what the costumer need/ ask applying less of effort. When we talk about validation, it doesn’t mean to ask to the customer if they will be aiming to use some product or to pay for it we try to promote product utilization you (usuability) between real customers.. 

At the same time this product should give metrics or information (data) that allows the stakeholders to learn about this service. 

This MVP enables a fully cycle of the feedback loop with the least amount of effort. 

It may lack many features, but it is built in a way that can be put in front of customers in order to gauge their reactions and test hypothesis.

MVP Objetives

• Avoids the creation/ build of a product that no ones wants! 
• Maximize the customer learning (don’t let the company goes in bankruptcy).
• Find proof and evidence before it’s too late for their entrepreneur.

An MVB helps entrepreneurs startups begin the process of learning, not ending it. 

It is design not to just answer products designed not to just technical questions, but also to test fundamental businesses hypothesis.

It is a challenge as we must to be willing to set aside our professional standards to start the process of validate learning as soon as possible. Put this doesn’t mean operating in a sloppy or on undisciplined way. 

We also need to prepare for the fact that MVPs often result in bad news. Unlike traditional Prototypes MVPs are designed to answer the full range of business questions and not just design or technical ones.

You will use your MVP to run experiments and the outcome of those experiments will inform you as to whether the hypothesis was correct. These experiment  should  provide you with enough evidence to decide whether the direction you are exploring to be pursued, refining or abandon.

“Stay agile work in a way you can adapt quickly to changes”

Measure behavior: Build your MVP in a way that you can observe and measure what people do. Talk to your users don’t look only for the what, dig deep and try to get to the Why! 

MVP HACKS

Create an MVP in four steps:

1.- As a team, define and discussed the first hypothesis in your list. 

2.- Try to understand the value of an idea or features to its core value proposition. 

3.- Prioritize according to the value proposition. 

4.- Prototype the idea and get feedback from users.