minimum-viable-product

What Is the Minimum Viable Product And Why It Matters

As pointed out by Eric Ries, a minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort through a cycle of build, measure, learn; that is the foundation of the lean startup methodology.

The origin story of the lean startup movement

It officially started with an HBR article of 2013 that referred to a new phenomenon in the business world “Why the Lean Start-Up Changes Everything:”

However, the origin story started in the late 1990s.

Steve Blank, a retired entrepreneurship“>serial entrepreneur had the time to think through about what he had missed in terms of business frameworks, during the years, as he started several high-tech companies. 

He had noticed that the only tool available at the time was the business plan. However, not only the business plan was a static document which didn’t survive the first contact with the real world. 

That document was also plenty of untestable and untested assumptions. 

The patterns he noticed would be all gathered into what became a manifesto, and the foundation for the lean startup movement.

This manifesto would be called, Customer Development Manifesto, and it moved along 17 principles.

It started from a definition of a startup that moves along those lines:

A Startup Is a Temporary Organization Designed to Search for A Repeatable and Scalable Business Model

The interesting part of this definition is – I argue – the “search for” part. In fact, many companies in the past started from a prepackaged business model they could apply to their business to scale up.

In the real world, startups need to look for a business model. The process of iteration to find a business model is as tough as the process of iteration of humans searching for meaning.

In fact, only when a startup has found the proper business model it will be able to unlock value in the long-run.

The birth of the Customer Development Manifesto

The Customer Development Manifesto moved around 17 principles:

  1. There Are No Facts Inside Your Building, So Get Outside
  2. Pair Customer Development with Agile Development
  3. Failure is an Integral Part of the Search for the Business Model
  4. If You’re Afraid to Fail You’re Destined to Do So
  5. Iterations and Pivots are Driven by Insight
  6. Validate Your Hypotheses with Experiments
  7. Success Begins with Buy-In from Investors and Co-Founders
  8. No Business Plan Survives First Contact with Customers
  9. Not All Startups Are Alike
  10. Startup Metrics are Different from Existing Companies
  11. Agree on Market Type – It Changes Everything
  12. Fast, Fearless Decision-Making, Cycle Time, Speed and Tempo
  13. If it’s not About Passion, You’re Dead the Day You Opened your Doors
  14. Startup Titles and Functions Are Very Different from a Company’s
  15. Preserve Cash While Searching. After It’s Found, Spend
  16. Communicate and Share Learning
  17. Startups Demand Comfort with Chaos and Uncertainty

The lean startup Manifesto would became the starting point for the evolution of The Lean Startup Movement. And the introduction of new tools and frameworks to use as an entrepreneur (Business Model Canvas and all its variations)

A glance at the lean startup methodology 

The lean startup methodology aims at creating a scientific, repeatable process for product development that allows the startup to build products and deliver them fast. In other words, the lean startup moves around three stages:

  • Build.
  • Measure.
  • Learn.

This process of build > measure > learn will need to be repeated over and over, thus creating a feedback loop. The main purpose is to initially come up with a minimum viable product (MVP), which is a critical aspect of the lean startup model.

As pointed out by Eric Ries:

A Minimum Viable Product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.

The MVP will be the foundation to build a successful company. 

What is not an MVP?

As Ash Maurya pointed out the definition of MVP got overtime simplified with the smallest thing you can build that lets you quickly make it around the build/measure/learn loop.

This kind of simplification brings to flaws and mistakes that can also lead to great failures.

For instance, Ash Maurya defines the MVP as “the smallest thing you can build that delivers customer value (and as a bonus captures some of that value back).”

Demo > Sell > Build: Tweaking the classic lean startup loop

When I spoke to Ash Maurya, author of Running Lean and Scaling Lean, we discussed how building a solution before validating it, might be at the basis of one of the most dangerous biases for entrepreneurs: the innovator’s bias.

As he pointed out, “one of the biases that that many entrepreneurs fall run into is this premature love of the solution. Like the first principles in science, you almost have to deconstruct an idea. We have to start with the basics. In this case, when we look at our business, we have to break it down into customers and problems.”

And he continued, “If you don’t have the right customers who are trying to get sorted and problem solved, and no matter what solution you build, it doesn’t matter because we know that unless you’re solving a problem, customers are not going to use it.

They’re not going to pay money. Even if you can reach them. Even if you have a patent or an unfair advantage, it doesn’t matter at the end of the day because your customers don’t care. So that is the way we logically break it down, but that innovator’s bias is one of those sneaky things.”

Ash Maurya proposed a slightly different approach: 

We might start with the demo. We might first go and find customers, see if we can reach them, even talk to them. Because if you can talk to customers, we can sell them anything. We start with the end in mind and then we deconstruct our way back to the beginning and start validating at a bottom-up level. That generally is how we overcome the innovator’s bias toward a solution.

running-lean-ash-maurya

As Ash Maurya pointed out “build a demo first, sell that demo and if you can sell the demo then don’t even build the product.”

Validating the market with a bottom-up approach to flip upside-down the product-market fit problem

This process helps to validate the market clearly, thus eliminating most of the risks associated with a company’s failure (people do not need or want that product).

This MVP approach flips upside-down the product-market fit problem. Where in a product-market fit scenario, we build a product first and we iterated times and times again to find this magic moment, called “market fit.”

In this leaner MVP approach we validate the market first, then build a product. Of course, that doesn’t mean success is guaranteed. We just moved the market risk away, and now the whole pressure is on the feasibility of the product that we demoed. 

A great example of this approach is how Tesla pre-sells its cars, by demoing them first, before going in a large-scale production: 

cybertruck-preorder-tesla

While the demoed product has already all the aesthetic and most of the features the final product might have. For a car company, one thing is to build a single car, another is to produce it at scale. 

On a much smaller scale, a demo might be a simple landing page, with the mock-up of the product you want to build. Once gain, this process will help us validate the market first. 

From there it will be more a problem of feasibility. Of course, the more a product is technically challenging the more the feasibility risk will be high, later on. However, that also means we saved massive financial resources.

As to produce that product, and make it go to market, we would have spent time, money and other people’s capital and yet build something people do not want. 

The leaner MVP approach is about finding whether the “commercial time-window” is right 

We might argue that the whole concept of leaner MVP is completely new. However, companies that have innovated in their fields have been using this approach all along (or at least the innovative units within those companies).

When I interviewed Alberto Savoia (he was among the engineering team of Google in the early years and before its IPO), he explained how back in the 1980s IBM thought “we want everyone to have personal computers.”

IBM thought there was no way that most people would use computers as they would not be predisposed to learn how to use a keyboard (an assumption proved wrong).

How to test this assumption? IBM thought to tackle the market, with a speech to text technology that enabled people to talk to computers and get that translated into text.

They figured a mechanism that could convert speech into text, would make a computer a potentially mass-market product. In short, people would dictate to computers, instead of typing on a keyboard. 

Yet, instead of focusing on building the product first (it would have taken years and many billion dollars), IBM devised a smart experiment.

The IBM team brought people in a room, they gave them a microphone, and there was a screen in front of that microphone and told them, “Look, this a new way of running a computer, there’s no keyboard, you just speak to it, and give it a shot and tell us what you think.”

Therefore, people talked and the computer would translate that into text. However, it wasn’t the final product, not even close. In the room next door, there was a human being, that got the input through the headphone, and typed it on a keyboard.

The effect was that the users in the experiment thought the IBM speech to text was a working prototype, but it wasn’t. 

With this simple experiment IBM collected valuable data, that told them a few things they were completely wrong about. First, people would not talk to computers for long, as they got a sore throat.

Also in an office environment, everyone talking loudly will not be viable (especially if you need to input in the computer confidential information). 

Those data points alone made IBM stop prioritizing on the speech to text experiment. And this would save them years of R&D, lost focus and financial resources.

A third assumption, would be proved wrong after a few years. Indeed, keyboards would eventually become mass-adopted, and an efficient way to use computers at scale! (and it still is today).

Voice-enabled device are going into mass-production only now (Alexa, Google Home, Cortana, Siri). However, this is a much different technological environment compared to the 1980s.

Thus, if at all this leaner MVP approach can tell us an extremely valuable piece of information on whether the commercial use case timing is right! (that for sure represents a good chunk of the product’s success in the first place).

It’s important to clarify that this approach will not tell us whether a product or technology will ever be successful in the future. Neither, whether this technology will be successful with another commercial use case.

In short, IBM thought the speech to text would be an alternative to keyboard and this assumption turned out to be wrong, for the time being. Had they thought another commercial use case would that been proved right? Maybe. 

But for what they needed back then (make PCs scale and become a mass product), text to speech wasn’t the right project to prioritize. 

When does an MVP become too risky?

If you just starting up, you don’t have an established brand and your reach is limited, the MVP might be the way to go. That’s because the risk of failure and the cost in terms of branding is very very limited.

Thus the value captured from the iterations and the feedback gained is high. All that changes, if you have an established brand and a broad reach.

That is where the Exceptional Viable Product definition given by Rand Fishkin (founder of Moz, and SparkToro) comes handy.  

As Rand Fishkin pointed out:

 I believe it’s often the right choice to bias to the EVP, the “exceptional viable product,” for your initial, public release.

Fishkin suggests creating an MVP but not releasing it until that is exceptional. At that point, you do release it to the public. Thus, the exceptional viable product (EVP) methodology requires an iteration of the product “in-house,” tested with your team and maybe a few selected customers.

Companies like Apple have been following this approach all along. Apple has been building its hardware products by testing them internally, as much as possible. 

There are two main reasons to opt for this approach:   

  • Brand risk: if you have an established brand, a new product, released to your audience it way too risky. As this might compromise the whole brand equity gained over the years.
  • Competitive risk: when you release a product to the market, even to a smaller subset, you’re enabling competitors to gain access to the new product you’re launching, thus giving away valuable information, that will give them a competitive edge, to quickly improve on what you’re doing. 

As Fishkin suggests, only when you’re sure the product is exceptional you can launch to a broader audience. The EVP methodology allows more established brands to avoid failures that can lead to irrecoverable loss of reputation. 

Enter the Exceptional Viable Product Methodology

exceptional-viable-product

As Rand Fishkin pointed out:

My proposal is that we embrace the reality that MVPs are ideal for some circumstances but harmful in others, and that organizations of all sizes should consider their market, their competition, and their reach before deciding what is “viable” to launch. I believe it’s often the right choice to bias to the EVP, the “exceptional viable product,” for your initial, public release.

Rand Fishkin also added:

Depending on your brand’s size and reach, and on the customers and potential customers you’ll influence with a launch, I’d urge you to consider whether a private launch of that MVP, with lots of testing, learning, and iteration to a smaller audience that knows they’re beta testing, could be the best path.

In other words, he takes into account two main variables. On the one hand, you have the attention, customers, and evangelism.

On the other hand, you have the product quality. The greater the attention, customers base and ability to evangelize the more you’ll need to have a solid product before its launch.

In Rand Fishkin vision, an EVP has to have two minimum features:

  • Have a decent exposure.
  • And be truly impressive, at least at one must-have – identified – feature customers are looking for.

He learned that lesson at Moz when he was trying to build a new tool to identify spammy links. As Rand Fishkin recounted:

Our research had already revealed what customers wanted. They wanted a web index that included all the sites Google crawled and indexed, so it would be comprehensive enough to spot all the potential risky links. They wanted a score that would definitively say whether a site had been penalized by Google. And they wanted an easy way of knowing which of those spammy sites linked to them (or any other site on the web) so they could easily take that list and either avoid links from it or export and upload it to Google Search Console through a disavow file to prevent Google from penalizing them.

That would be anexceptionalproduct.

But we didn’t have the focus or the bandwidth to build the exceptional product, so we launched an MVP, hoping to learn and iterate. We figured that something to help our customers and community was better than nothing.

I think that’s my biggest lesson from the many times I’ve launched MVPs over my career. Sometimes, something is better than nothing. Surprisingly often, it’s not.

Connecting the dots between MVP, Leaner MVP and EVP 

The lean startup movement and the lean startup methodology gave an important contribution to the startup ecosystem. A core part of the lean startup methodology is the MVP.

As we’ve seen throughout the article an MVP is the classic mode of experimentation for startups. It has been a very powerful shift as it enabled companies to start gaining customers’ feedback early on in the product development cycle. 

Yet, as we move toward, the leaner MVP approach has taught us that we can use an approach that is even more bottom-up by demoing the product even before we’ve built it, to see if people want it. 

This approach moves from build > measure > learn to demo > sell > build. 

The leaner MVP approach will work well to remove market risk away, while putting more pressure on the feasibility risk. And yet, it will help us save valuable time and resources. 

Both an MVP and leaner MVP approach become risky when it comes to an established brand with a wide audience and reach, where a new product release, also if circumscribed to a small audience, can spread quickly.

In that case, an EVP approach will help, as it will focus on iterating the new product with specific units within the company, and with only few selected customers. 

Other business resources: 

Handpicked business models:

What is minimum viable product in Agile?

As pointed out by Eric Ries, a minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort through a cycle of build, measure, learn; that is the foundation of the lean startup methodology.

What makes a good MVP?

A great MVP is something that delivers enough value to potential customers, thus ready to be launched and as result gather feedbacks from those potential customers to improve it fast.

What is an EVP?

As Rand Fishkin pointed out: “MVPs are ideal for some circumstances but harmful in others, and that organizations of all sizes should consider their market, their competition, and their reach before deciding what is “viable” to launch.” Thus EVP, or “exceptional viable product,” might be the most suited choice for an initial, public release.

Published by

Gennaro Cuofano

Gennaro is the creator of FourWeekMBA which target is to reach over two million business students, executives, and aspiring entrepreneurs in 2020 alone | He is also Head of Business Development for a high-tech startup, which he helped grow at double-digit rate | Gennaro earned an International MBA with emphasis on Corporate Finance and Business Strategy | Visit The FourWeekMBA BizSchool | Or Get in touch with Gennaro here

2 thoughts on “What Is the Minimum Viable Product And Why It Matters

Leave a Reply