What is the concept behind an MVP?

What is the concept behind an MVP?

What is the concept behind an MVP? And why do companies continue to use this model when creating their products and their services?

By Fabrique Agile

 

Back to the blog →

An MVP, or minimum viable product, is a key concept in the Lean Startup methodology. It allows you to quickly identify opportunities with high growth potential and establish a development plan for your initiative. An MVP is a prototype of a product that has just enough functionality to satisfy early customers and provide feedback for future development of the real product. The idea behind an MVP is that if you build something that is too complex or too advanced for your target audience, you’ll end up spending more time building it than you need to and you’ll be targeting the wrong problem, the wrong customer. By launching a minimally viable product first, you can begin to build a community of early adopters around your product, which allows you to get feedback on what features they would like to see and continually improve the product based on that feedback.

So, it’s important to note that an MVP is not an unfinished product; it must solve enough problems that your users are willing to pay for it. The most important aspect of an MVP is that you only build what is minimally viable for your first customers. This means refraining from adding features (even if they are necessary) and avoiding over-developing the solution.

Main elements of an MVP

  • Depending on the type of MVP, the prototype proves or solves a basic problem for a group of early adopters.
  • It contains only the basic functionality needed to serve a group of users (early adopters).
  • It can be produced quickly and tested with real users.
  • It is imperfect, that is, it can be improved as you test it.

Examples of MVPs

It is increasingly common for companies to use MVPs as a way to reduce risk. When developing a new product, service or feature, companies can create an MVP and send it out into the world as a test. This allows them to see if there is interest in the product before investing too much time and money in it.

Here are four classic examples of MVPs:

MVP Amazon

The first version of Amazon.com was a simple online bookstore that allowed users to select books, put them in their virtual shopping cart and make a transaction with their credit card. This allowed the company to test its e-commerce concept without having to invest in creating a product management or inventory control platform…

Coca-Cola tested more than 100 flavors and different bottle designs before choosing the ones we know and love today.

MVP Coca cola
MVP Airbnb

Before Airbnb became “Airbnb” in 2009, a year after its launch, it was “Airbed and Breakfast”. Two years later, the company started sending professional photographers to homes and realized that homes with beautiful photos received 40% more bookings. Over time, they gradually added new features. Today, Airbnb is an online travel agency with over 2 million listings in 190 countries, but it started very small.

Dropbox also started small and simple, offering users only a landing page to validate interest, leading to incremental development. Additionally, the company offered only 2 gigabytes of storage space for their files. To reach potential users, they made a video showing what the service would look like if it was built. They launched this video as a “product” and then started getting sign-ups from users who wanted access to it when it was ready. This gave them enough money to build the actual product (a file sharing tool), which they later launched and started working on based on user feedback. Dropbox then grew by adding additional features that users wanted, including file sharing, photo galleries, etc.

MVP Dropbox

The MVP concept can be applied to any stage of product development. This means that you can adapt the MVP concept for use from problem validation to the integration of new features. Here are some other examples, less formalised but more entertaining, that we suggest to inspire you:

MVP
MVP

‘Hand of God’: Brazilian Nurses Use Gloves Filled with Warm Water to Create ‘Human Touch’ for Covid-19 Patients Source : https://www.news18.com/news/buzz/hand-of-god-brazilian-nurses-use-gloves-filled-with-hot-water-to-create-human-touch-for-covid-19-patients-3622187.html

How can you use the MVP?

You can use the MVP throughout your product development process. The MVP will help you confirm many types of business assumptions:

Validate the existence of the problem your product will solve

An important element in the concept of an MVP is that it is something that proves that your solution solves a problem for the user or customer. This can be a physical product, a digital service or a feature of an existing product. The key is that the idea is validated by the customer through continuous feedback. You can do this by showing your solution and observing the behavior of the potential consumer. Also, you can create surveys or conduct problem interviews.

Estimate the size of your market and confirm if your solution answers the identified problem

A minimum viable product will help you confirm whether or not there is a market for a solution like yours. Although it may seem counterintuitive, an effective MVP is not necessarily the simplest possible version of your product. Rather, it is the version that allows you to start learning what works and what doesn’t with real customers who will actually use your product. This version of your product will help you find out if people will buy what you are selling. You can use a template, a prototype or do solution interviews to gather information about how your target audience sees your solution.

Include the customer in the product development process

It’s good to be able to launch something quickly, but it’s even better if you do it right and involve the customer in the process at an early stage. If you can involve them as early as possible in the product development process, you will be able to increase your success rate. The reason is that a company that takes this approach shortens its time-to-market, reduces development costs and risks.

Start developing your business model

If you are an entrepreneur or small business looking to develop a product or service, the MVP is an extremely valuable tool that will help you understand the answer to many questions such as: “Will people buy my product?”, “How much money are they willing to pay for my product?” or “What forms and channels of payment should I accept?”

The MVP is a practical product development tool that is used by many companies as they grow. An MVP helps entrepreneurs get started on developing a project with minimal investment of money and time. It allows founders to spend less money during product development and ensure they are building something their customers want before investing more resources into it.

In this post, we shared ideas on how to use minimum viable product in developing your business ideas. If you’re ready to start building your minimum viable product, we invite you to check out the MVP types in our experimentation mapping.

5 cognitive behaviors that prevent experimentation in your company

5 cognitive behaviors that prevent experimentation in your company

5 cognitive behaviors that prevent experimentation in your company

By Fabrique Agile

 

Back to the blog →

Avoid these five common mistakes when validating a new business idea.

Every business needs to innovate. Ultimately, faster learning companies will keep up with the competition and win. But that’s much easier to say than to do. As strange as it may seem, many companies don’t know what to do. There are many causes for this: lack of tolerance for failure, decision-makers not taking risks, staff needing constant feedback, or nobody who knows how to start or keep up the momentum of innovation.

A new business model, a new product, and a way to make an impact is what we need to succeed in business. Business leaders and product development teams are often looking for the next big thing, but when it comes to experimenting with new ideas, they run into cognitive biases that become impediments.

The attribution bias

Have you ever heard of the attribution error? It is a cognitive bias that occurs in people when they try to explain why something has happened. More precisely, we tend to attribute responsibility for failure to outside parties (such as bad luck or other people) and credit for success to inside factors (such as our own work or skill).

And this affects the way we view business experimentation.

Using the attribution error, when our experiment failed, we can blame it on the fact that the experiment wasn’t really suited to our business in the first place. When it succeeds, we pat ourselves on the back for being so brilliant for thinking of it in the very first place! I mean, how smart were you?

But here’s the thing, if an experiment doesn’t work, it doesn’t mean it’s pointless. If it’scsuccessful…well, identify the elements that contributed to the achievement. In both cases, there are learnings and reflections that will improve your experience.

Confirmation bias

Confirmation bias is a natural instinct to search out and believe information that confirms your beliefs. When making business decisions, this tendency can be very risky, and it is the origin of the confirmation bias.

Business experimentation is an important way to ensure that innovation in your business works properly, but it can be difficult to determine accurately if something is not working when you are biased toward one outcome over the other.

Confirmation error occurs when you fail to gather and consider conflicting evidence because of your own personal biases.

This can lead you to overestimate the magnitude of an effect, or even ignore a problem in its entirety! This can lead to an ineffective product or service, or even complete failure.

The Kruger Dunning Effect 

There’s a common prejudice that’s making the rounds in the business experimentation area and it’s high time we addressed it. The Kruger Dunning Effect is the idea that if you do a lot of experiments, your results will become increasingly unfavorable.

How does it work? Let’s say you’re testing a new message on your landing page. You run two experiments with similar message concepts, one after the other. The first test does not perform any better than the control test, but the second test shows a significant increase. How do we know what is going on? Is it because a different message worked better? Or is it because the second experiment didn’t reach all the people who had been feeling negative in the first test?

It’s hard to know for sure, but there are ways to control for this bias, including running multiple experiments at the same time or phasing them to allow time to analyze your data.

 

Optimism

Optimism is a cognitive bias that leads us to expect the best outcome in all situations, regardless of its probabilities. Optimism can be helpful in some circumstances, such as when we try to stay positive and optimistic about daily problems. However, in other cases, optimism can lead us to make decisions that are not based on fact.

For example, let’s say a company has spent the last three years working on a new product line. They have done all the research they can think of and are confident that their new product line will be a great success. But when the time came to release the products to the market, no one was purchasing them! The company did not receive any negative feedback from customers, on the contrary, everyone liked them! So why did the sales not work out?

The company was too optimistic about the success of their product. They were so sure that people would buy that they didn’t explore different opinions to challenge their value proposition. In addition, the company did not think about iterative methods to validate their value proposition even before trying to get their products into stores. So when customers didn’t buy their products, the company didn’t have any other hypotheses to test to correct the situation fast enough and have their product pivoted.

Commitment Theory 

The commitment theory states that the more you invest in a particular project, the harder it is to give up on that project and to explore other opportunities.

This can be risky in the business world, where experimentation is essential to remain both competitive and profitable. One company that has demonstrated this risk is Kodak: it invented the first digital camera, but failed to capitalize on it because it was too focused on its film-based products.

Letting go of cognitive biases when experimenting with business is critical to a company’s growth. Having a neutral, evidence-oriented posture requires skills that cannot be learned overnight. However, the roadmap to innovation can easily be planned: it all starts with inculcating a mindset that promotes constant business agility and promotes the development of products that provide value to the user.

 

 

In this article, we looked at five cognitive biases that can affect your approach to business experimentation and we discussed when people may be experiencing them. Consult our business experimentation map! You will find a lot of free resources to support and accompany you in your daily business experiments.

Business Reinvention Through Experimentation: Case Study CollectSpot

Business Reinvention Through Experimentation: Case Study CollectSpot

Business Reinvention Through Experimentation: Case Study CollectSpot

Par Fabrique Agile

 

Retour au blogue →

When you don’t find a right fit to get into new markets, business reinvention through experimentation can uncover new opportunities for your product or service.

 

Overview

CollectSpot is a product of the Brazilian company Entregali based in Sao Paulo whose main service is to facilitate the shipment of parcels through distribution points located in local businesses close to the end user.

Open to exploring new horizons for their product, due to the move of one of their members to North America, the team decided to evaluate if the value proposition could fit in the North American market through the Fusion Challenges program. However, although they determined that this new market was not attractive to them, the business exploration allowed them to improve their value proposition in Brazil, positioning themselves more strategically in the local parcel delivery market.

For this reason, validating the product-market fit before starting to develop an adaptation of the product to another market is always a step forward.

 

Needs

To implement its service in Brazil, CollectSpot had to overcome bureaucratic obstacles imposed on companies interested in receiving and storing the parcels. For this reason, one of the first needs of the team was to validate less bureaucratic rules in the context of Montreal.

On the other hand, another challenge for the team was to explore whether the proposed solution could have the same impact achieved in Brazil and find a way to insert their proposal in the Quebec market.

 

The process

Through the Fusion Challenge program, CollectSpot had the opportunity to meet key people and do Quebec market research to explore the potential impact of their proposal in Canada.

First, the team was introduced to the implementation of the business experimentation culture (link on french only) from the customer’s point of view, in order to put themselves in the customer’s shoes to empathize and understand the user’s problem.

Next, they were guided on how to apply the principles of the Lean Startup and to work in experimentation cycles in order to make decisions based on the data obtained.

The tools used by the team were the problem validation interview and exploratory meetings with potential clients, as well as with key people in the ecosystem of the target country.

“It was really helpful not only when it comes to understanding how the Canadian ecosystem works, but also to test the viability of our company in this new market. We were able to, in a smart way, go through the analysis of our competition in detail. Fusion’s support throughout this process was remarkable as they put us in touch directly with renowned Canadian professionals”, said Thiago Lopes, CTO of the young company.

Thanks to the important feedback received, CollectSpot realized that in the Canadian market in Montreal there was no major problem that its proposal could alleviate, thus invalidating their initial hypotheses. Therefore, its proposal had to look for other markets or evolve.

CollectSpot product

Pivot

Once they realized that their solution didn’t fit in the Canadian market, and based on experimentation and hypothesis invalidation guided by the Fusion team, CollectSpot decided to return to Brazil to take a step forward by proposing a new service offering to solve the problem of receiving parcels. In other words, business reinvention through experimentation.

“We had the chance to reach professionals in the fields of immigration, financing, market specialists and even representatives of Brazil’s local consulate. Most likely we wouldn’t be able to reach that many stakeholders acting independently. On top of that, Fusion’s team provided us with mentorship and valuable feedback that we applied even on the development of the company in our home country, Brazil”, added Thiago.

After several prototypes, and taking advantage of their expertise in hardware, research and development, as well as web development, CollectSpot members proposed a locker with different types of capabilities, accessible through a password system, which can be installed in residential condominiums.

 

Results

Through the cloud platform developed by the team, CollectSpot generated value for residential condominiums, eager to guarantee their customers easy access to received parcels. This pivot allowed the company to solve the problem of receiving parcels in a different way, thus positioning itself in a more strategic place as a startup, since it proposed the space to facilitate the delivery and reception of parcels.

Once the solution was implemented in its home country of Brazil, CollectSpot saw this value proposition quickly gain traction. Currently, the company is focused on closing several contracts under the new solution.

“The main outcome after our immersive participation in Fusion Challenge in Montreal was the realization that if we want to start a last mile delivery business in North-America, we need to develop an IoT solution to differentiate CollectSpot from local competitors and to get ahead in the technology and the convenience offered”, said Raquel Schramm, CEO of CollectSpot.

Perhaps one of the great changes obtained by the CollectSpot team was their mindset as entrepreneurs. Not being limited by seeing how their proposal did not fit in the Québec context, but taking advantage of the learning obtained to improve the original proposal that was already generating an impact in Brazil. Quick learning, finding business evidence through experimentation cycles, is an important element when it comes to exploring and materializing a business idea.

To build a good value proposition: think about the problem, not your solution!

To build a good value proposition: think about the problem, not your solution!

To build a good value proposition: think about the problem, not your solution!

Par Fabrique Agile

 

Retour au blogue →

What a relief when you get to scratch exactly where it itches. Has this happened to you? The best thing is the feeling of satisfaction that comes immediately after scratching, an “ahhhhh” of relief. This is precisely the desired effect when you are about to create a business, to overcome a real user problem.

 

However, for a good portion of entrepreneurs, especially those who are still in the development stage of their business idea, this attitude is usually not evident. They base their entrepreneurial spirit on the solution they want to bring to the market rather than the problem it will solve.

 

Practice rather than theory

To successfully build a business, you have to act, take action. Turning an idea into a business depends on how it responds to the user’s jobs to be done. That means if this idea solves a real customer problem.

Despite the theory and practical exercises, among entrepreneurs in the start-up stage, it is common to find certain postures more focused on the solution to be offered than on the problem to be solved.

 

A real-life case

Let us present the case of the “Hazelnut” team, whose product was chocolate, very focused on the solution it wanted to provide (its chocolate), but not on the problem it wanted to unravel.

 

Their hypothesis: the story behind the product

“Why would the public buy your product”? When the “Hazelnut” team asked themselves this question, they replied that people would buy it because of its artisan and traditional manufacturing. For them, the value proposition was the way chocolate was produced and the tradition behind it.

This is where making an entrepreneur “in solution mode” into an entrepreneur “in problem mode” becomes a challenge. When the value proposition is not solid, nothing better than to go through experimentation to find meaning in the offer that is being built.

 

Experimental approach: exploring the market to validate the hypothesis

In this context, during the hypothesis validation stage, this team decided to conduct a survey as a market exploration activity. During the development of the survey, the team members realized that their value proposition was not strong enough, since it did not solve a real user problem. Their hypothesis was more related to the quality and origins of the cocoa, but they have gathered evidence from customers that points to other important criteria. They thus discovered other reasons for consumers to buy: the chocolate composition (organic), price, distribution channels, among others.

When you are working on ideas to develop a product, you must consider it as the means that your customer will use to solve or complete a task or job (in this case, the urge to consume chocolate). That is, consumers are not buying a product, but rather something that helps them make their lives easier.

 

Learning: take a step back and listen to the customer

The “Hazelnut” team members realized that they needed to take a step back to better understand their potential customers. Instead of trying to “impose” their vision of the value of the product, they put their focus to find out how to respond to the value that the user is looking for in their product. It is this turnaround that is sometimes difficult for entrepreneurs to adopt. You have to start from the customer’s needs to fuel the development of the solution, and not the other way around. Once the “Hazelnut” team met its potential users, real answers were able to guide them so as not to launch a product that would not have had traction. Here is a way to avoid potential risk in starting a business: test to keep away bad assumptions during the validation phase of the problem or problem market fit.

Although they were start-up entrepreneurs, they had the flexibility to challenge their own hypotheses thanks to the experimental method, right from their first cycle of experimentation. In this way, they began to collect evidence, and they had the courage to go back to assess value generation scenarios for their target. And above all, they put themselves in a position of empathy towards the customer and the market.

 

This is why it is essential as an entrepreneur to put energy into a good understanding of the problems of our target audience, those “jobs to be done” or small tasks that the client seeks to accomplish. There are several tools to identify these jobs to be done: among them, the problem validation interview which is quite used during the exploration stage. If you are successful in helping your user with their issues, it will result in a positive impact. The first step in this direction is to embrace a culture of experimentation. Why? Because this posture is based on understanding the user’s real irritants in order to experience and generate value, which brings you closer to developing a long-term relationship with your client.

As a bonus, we share a video on this unmissable topic: Culture of experimentation and innovation (only in French, but with the option for subtitles).