Minimum Viable Product (MVP) is a term that regularly causes confusion and that’s why we answer the questions in this blog: what exactly is an MVP, how do I identify it and why should I develop an MVP?
Minimum viable product
An mvp viable product is the most minimal version of a new product with which the preparation team can gain maximum knowledge. An MVP is therefore worked out from the core idea of concrete idea before the app originated. You look for an answer to the question: what is my client’s use?
“A minimum achievable product is not a product but a process” – Eric Ries
The focus is therefore on the (problem-solving) features that are essential for the success of the app and cares for the different ability. A well-known example of this is Flitsmeister, the app that has been warning the majority of the Netherlands for speed cameras on the roads for a few years. The app is constantly being expanded with her and his users of matrix signs on the highway, but the developers have never lost sight of the core: informing users about speed cameras.
What is not an MVP?
Prior to going deeper into what an MVP is, we must first have a clear understanding of what absolute is MVP is:
- The test of a few minimal prototypes and then 100 beta users is not an MVP
- Processing a set of minimal features that are not viable (collectable) in your (web) app is not an MVP
- Building a few mock-ups and showing them to public users is not an MVP.
- Another common assumption is that in the first phases of a project no working product is delivered. You are still in the WTF phase (see image below) and therefore not yet in the MVP phase!
An MVP is the product version of a product
How does anyone give me a successful MVP?
It is an MVP step forward when identifying a problem. The MVP is then developed to address this discussion. The well-known words of Simon Sinek are also applicable here: focus on the why, instead of the what. Many failed projects focus too much (of just) on the what and how part, instead of focusing on what is really important: why are people going to use this? Click here for an MVP strategy in 12 weeks.
You can see this initial phase as an experiment: which functions are given priority and which do you exclude first? To answer these questions you have to make assumptions, take risks and experiment. Try to get answers to the following 3 questions:
- Why do people want to use this?
- Who is the target group?
- What actions do you want to perform?
- Minimum viable product crops
Be careful not to take a lot of hay on your fork at the same time. Then even take a break and prioritize things from essential to unnecessary.
Why an MVP?
- Receive feedback in the very first phase of product development (early adopters)
- Faster knowledge of internal market as a product
- Less wasted mobile hours
- Get the product to the target group as quickly as possible
- Basis for other products
- Test in advance whether the developer really has the skills to create a valuable product