What is an MVP and Why Your Startup Needs One
Table of content
What is a Minimum Viable Product?
Discover the thirteen types of MVP
High-fidelity MVP
Low-fidelity MVP
The skateboard version of the product
A few years ago, an Agile and Lean coach Henrik Kniberg published a book on the methods of product development. An illustration from this book has been published dozens of times. It describes the basic principles of Minimum Viable Product:
How does MVP work?
Pros and cons of making an MVP
How to make an MVP for your business
Four life hacks for a quick start
Rule: Always divide the MVP by eight
Examples of successful MVP companies
Buffer
Airbnb
Twitch
Summing up
What is a Minimum Viable Product and why should any business start with that? Let’s dive deep and discover different MVP types, examples, and use cases.
Back in 2005, YouTube was created as a video-dating website. And Instagram was initially called Burbn (as in an alcoholic drink, yes). It was meant to be a planner that allowed users to check in at some places they were hanging out with friends, upload photos from their meetings, and earn points.
Neither of the ideas, however, panned out. Therefore, both companies conducted a performance analysis, paid attention to the users’ feedback, and finally pivoted. Essentially, the video-dating app and Burbn were acting as companies’ minimum viable products, or MVPs.
What is a Minimum Viable Product?
The term Minimum Viable Product was first introduced by Eric Rees, the famous American entrepreneur and the inventor of the Lean Startup. MVP is the basic version of the product that is just enough for testing.
In short, the concept of MVP illustrates the idea “Dream big, start small”. It is based on incremental software development that is being tested in real user conditions with every iteration. In that case, feedback helps the company mitigate risks at an early stage, avoid mistakes, and make sure there’s a market demand in advance.
Here are the traits of a top-notch MVP:
- This product should have just enough value for consumers to start using it eagerly.
- It should have the basics of the future product, thus intriguing users enough to make them look forward to the final launch.
- It provides the company with feedback on the quality of the product, which helps to take into account all the shortcomings and improve the final version.
Every stage of development should take the product to the next level. Then, the customers step in to test the product and share their feedback on any possible improvements. Thereby, MVP is instrumental in testing new hypotheses and eliminating poor decisions that could destroy the whole business.
The quest for good ideas is not a linear process. Conversely, it consists of several looped iterations that sometimes can lead to the next level. In total, there are six steps:
- looking for a problem,
- finding solutions to the existing problems,
- prototyping,
- testing,
- gathering feedback,
- making changes.
Every step can turn out to be a loop. You should go through every stage, again and again, sometimes taking a couple of steps back if the hypothesis doesn’t work. And if the original idea proved its inconsistency during testing or feedback stages, it’s high time for a company to pivot.
Discover the thirteen types of MVP
The purpose of the MVP is to test the future product on a live audience. Therefore, the quality and accuracy of test results can impact the speed and efficiency of the development. That’s why the types of Minimum Viable Product are divided into two groups: low-fidelity and high-fidelity. They can be merged and used simultaneously.
High-fidelity MVP
High-fidelity MVP requires better preparation, more resources involved, and detailed analytical work. They are used for:
- defining and optimizing a marketing strategy,
- testing the value proposition, communication channels, CTA,
- searching for potential growth strategies,
- finding first customers and the perfect niche market,
- analyzing demand for the future product.
Types of high-fidelity MVP:
- Concierge. The users are guided inside the product by developers instead of automated algorithms. It is perfect for AI development projects.
- Wizard of Oz. It is similar to the Concierge MVP but more advanced in terms of quality. Product management is also carried out manually, but the product looks like a working solution.
- Piecemeal. A few missing parts of the code or functionality are automated, while the other part of the product is still controlled manually.
- One painkiller feature is focused on a single problem. This is a simplified solution that kills only one specific pain of the client. Later on, it is possible to develop and scale this product into a more complex one.
Low-fidelity MVP
As its name suggests, the next group is characterized by low fidelity and simplified methods of gathering intel. They do not require careful engineering and large financial investments, so they lead to less accurate results. Their main purposes are:
- studying the practical value of the product,
- finding the most effective and on-fire solutions to the problem,
- helping identify and understand the client’s needs,
- conducting a niche analysis and understanding whether the juice is worth the squeeze.
Types of MVP with low-fidelity:
- blog,
- forum / community,
- survey / questionnaire,
- landing page,
- video tutorial,
- advertising campaign,
- presentation / slide deck,
- crowdfunding campaign,
- idea spotting network.
The skateboard version of the product
A few years ago, an Agile and Lean coach Henrik Kniberg published a book on the methods of product development. An illustration from this book has been published dozens of times. It describes the basic principles of Minimum Viable Product:
The upper half of the illustration shows an incorrect and ineffective way of creating a product. The principle is as follows: the client expresses the need for a vehicle that will help them move comfortably and quickly over long distances. We’re highlighting the main traits of the product:
- comfort,
- the possibility of making long trips,
- speed.
The company suggested that the best fit for this request would be a car. The development of prototypes has begun. However, each presented prototype wasn’t usable at all. Until the moment of receiving the final product, the client has never been satisfied with the iterations, because they could not use them and provide any feedback.
In the lower half, the developers are sending the skateboard to the client. This is still far from ideal: it is uncomfortable, slow, and you won’t get too far with it. But it’s working — albeit not ideal — means of transportation. The client can already use it and offer some thoughts.
In this example, the skateboard is the Minimum Viable Product. But of course, it represents whatever you are selling. By the way, because of that picture, many people started calling their first MVP a skateboard version.
How does MVP work?
The gradual evolution of the product that maintains usability helps developers immediately test the hypotheses. If it is uncomfortable to move around on a skateboard, then what about a scooter? If the scooter can’t speed up, will the bike cope with the task? Every next prototype solves one of the customer’s needs and/or increases the efficiency of existing characteristics.
Continuous contact with the consumer gives access to intel about possible bugs and flaws. But when the prototypes are not tested on direct users, the final product inherits the errors of the first stages. Fixing bugs after the sales launch will hit the budget harder compared to the situation when this ideal product was being developed from scratch. In this sense, the Minimum Viable Product method corresponds to the principles of Lean. It detects the simplest and cheapest solutions in the shortest time.
Sometimes, the customer can be satisfied with the product already at the motorcycle stage. That would mean that it makes no sense to develop it up to the car stage. This stage is called the Minimum Loveable Product, i.e. the minimum product that can make the buyer satisfied. The ability to find this milestone will save the startup a lot of resources and time.
But even when the final product becomes the same car that the developers described to the client at the beginning of the journey, the equation develops in favor of all market participants. After all, useful insights were collected and bugs were eliminated in the process. This means that the customer will receive a car of higher quality than originally planned.
Pros and cons of making an MVP
Here is a list of the main advantages of implementing Minimum Viable Product in your business processes:
- Resource optimization. By testing the Minimum Viable Product on real users, the company detects errors at an early stage. This allows you to better plan budgets, adjust the business model, and spend less time. Every next iteration becomes much more efficient than the previous one. Customers receive a quality product that meets their needs.
- Early customer acquisition. Testing each iteration on real people helps to find potential buyers even before the start of sales. When consumers use the minimum set of characteristics and functions of MVP, they have the opportunity to assess the potential of the future product.
- Increasing the correspondence between supply and demand. According to the statistics of CB Insights, 42 percent of startups are unsuccessful due to a lack of demand in the market. This means that the problem solved was not painful enough for the consumer. It is very important to understand customers and notice their troubles. Minimum Viable Product helps the company to bring its product as close to the needs of the market as possible.
- Improving investment potential. Investors are more willing to consider a real MVP than unrealistic fantasies that only exist on paper. The ability to use a prototype of the product and get acquainted with its basic characteristics makes the project more attractive for investment.
As for the disadvantages, there are only two of them — and both are significant.
- Software > hardware. The task of creating an MVP is most feasible when developing software. However, this doesn’t mean that MVP can’t be applied to material objects. For example, the largest automobile concerns (Toyota, Tesla, etc.) create dozens of prototypes before releasing a new model.
- Incompatibility with innovative products. When Henry Ford invented a car, communication with customers would not have brought him any benefit. At that time people still moved on horses and would have preferred to improve carriages, wheels, and carts. Therefore, revolutionary solutions that can change the market or even the whole world are difficult to prototype.
How to make an MVP for your business
Michael Seibel, a CEO of the famous accelerator Y Combinator, identified 4 factors of the perfect MVP:
- Work must be executed within weeks instead of months.
- There should be extremely limited functionality which only solves some problems.
- The MVP target audience is a narrow group of users instead of all the potential users at once.
- The MVP provides a starting point for further iterations.
According to Michael, most startups can start working extremely quickly — just a landing page and a Google spreadsheet are enough. He also explains that an MVP is just a starting point: there should be no magic, no special feature in it. You just need to start somewhere. And the beginning should be as ordinary as possible.
Four life hacks for a quick start
To create an MVP in a short time, Michael suggests the following steps:
- Determine the time frame of the brief specs. Let’s assume that the first testing of Minimum Viable Product is scheduled in three weeks. Then the terms of the subtasks within the brief specs should also meet in three weeks. This will give the workflow some certainty and allow you to abandon unnecessarily time-consuming steps.
- Write down your brief. The original idea of an MVP can change a lot. Sometimes it does so in the process of development. Imagine a situation: a founder tells investors about their concept, but in response, they hear, “This will never grow into a good company!” Then the founder begins tweaking the settings of their MVP, and the three-week deadline stretches to three months. When it takes this long, the changes may become invisible to either the team or the founder. So if you write down the idea of an MVP on paper, it will provide a stable zero point to which you can return at any time.
- Shorten the brief. The three-week deadline is nearing its end, and the team has not completed even half of the planned work. In this case, you need to throw out unimportant steps from the brief and focus on what is left. When the unimportant tasks run out, you will have to throw out the important ones too. At this moment, a startup needs to show at least something. Even an unfinished Minimum Viable Product will help you gain momentum. Postponing the start is much easier, but this path leads nowhere.
- Don’t fall in love with the MVP! This is just the basis from which you will develop further, often through pivots and a complete change of concept. It’s almost as if you fell in love with an essay you wrote in the first grade. Leave yourself some space for growth and do not linger at the starting point.
Rule: Always divide the MVP by eight
The creator of the Lean Startup concept Eric Ries reports: the main task of Minimum Viable Product is to offer the consumer a usable, testable minimum to start a cycle of studying their needs and reactions. However, Eric Ries believes founders usually start with too large projects. They have more features and functions than you need to start. And the larger the project, the more difficult it becomes to understand what exactly consumers did not like.
Eric Ries gives the formula for calculating the perfect MVP. “Take what you think is a good idea and cut its features in half. Then repeat it twice, then ship it back.”
Most likely, customers will perceive the minimum product negatively. In the end, it is 8 times less than what was originally planned. But the main goal is to make sure that consumers experience specific emotions about the product, a specific “like” or “dislike”. In this sense, the worst enemy of the founder is indifference.
Examples of successful MVP companies
Buffer
Buffer is an application for managing accounts in social networks and creating deferred posts on Twitter, Facebook, Instagram, Pinterest, and other platforms. This app includes analytics and audience interaction features.
At the very beginning of development, its website looked like this (on the left). However, this version was not effective enough, and it is difficult to call it a full-fledged MVP. Therefore, the offer was upgraded with an additional page (on the right):
The customer’s interest immediately jumped from “Well, this is interesting” to “I want to buy it.” The founder of Buffer Joel Gascoigne stated, “After this result, I didn’t hesitate to start building the first minimal version of the real, functioning product.”
Airbnb
This is what the Minimum Viable Product from Airbnb looked like:
At the very beginning, the service did not have a built-in payment function, and users met directly with the owners of the property and gave them money. Also, there were no built-in maps on the website that would allow you to see the location of rented apartments and houses. Finally, the company’s CTO, who was responsible for the code, worked part-time.
Twitch
The Twitch streaming service began as a platform for broadcasting the online show Justin TV. At that time, only one channel was available: a live broadcast from Justin’s life. If users didn’t like Justin, they had nothing else to do on this website: all the functionality was limited to one stream.
At the same time, the video itself was of extremely low quality — as the founders recall, it was barely possible to recognize the face of the main character on it. And, of course, back then Twitch was extremely far from the gaming and streaming industry.
Summing up
MVP is a prototype of your product, a demo version that can be tested on real customers. Within each iteration, you receive feedback from your users. This allows you to study the shortcomings of the product and offer an increasingly effective version with each new stage.
The three most important questions that the founder must answer before creating an MVP:
- What problem am I trying to solve?
- Who am I trying to solve it for? Who is the consumer?
- What does my skateboard version of the product look like?
The Minimum Viable Product should be as simplified and primitive as possible. Its main task is to start a cycle of communication with customers, initiate the workflow.