Skip to main content

MVP is often misunderstood. Try MVE - minimal viable experiment


By now everybody should be familiar with the concept of an MVP? Are you?
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. Eric Ries
Good. Now remember the last time you did an MVP. What was your goal? What should have been your goal?


Problem with a word "Product" in the MVP

Remember last time you've used MVP acronym? What was the context? Learning, obviously. Yes? Well, I hope so. Because last time I've heard MVP in a conversation was something along those lines: "... let's just release it as an MVP, see if anybody gonna use it and then take it from there". I was nodding in agreement and only an hour later it got to me: "Did we just called version 1 of the product an MVP?".

One word makes a difference for an understanding

What is a product? Something you can package and sell, right? So in the context of an MVP, "Product" makes us focus on features, presentation and value proposition. While we know, or should know, that we need to be focused on learning only. And that's crucial. To learn something about your product idea you don't need to build anything.

Minimum Viable Experiment

So let's just change one word and see if that's gonna help the understanding. Steven Cohn, the founder of the "Validately", did just that and proposed MVE.
What’s the MVE you ask? Well, it is a prototype or a concierge MVP or anything else that you can use to validate or invalidate a product hypothesis.
Yeah, don't read too much into that. Change just one word. But this change might set significantly different expectations. It's not the product anymore, it does not need to look, does not need to work or to convert. It's an experiment. It needs to prove or disprove a hypothesis. And after you'll have all the learning from it - just throw it out the window.

When is MVE better? 

When "build" part is not an option for you.
As  Nis Frome puts it:
Product teams in large companies are not as nimble as startups due to increased layers of communication and decision making, and increased brand and legal risk, among other factors. For enterprise product managers, validated learning comes far more rapidly utilizing other strategies. Instead of a “Build-Measure-Learn” approach, enterprise product managers need to take an “Experiment-Measure-Learn” purview.

Will MVE help me? 

Depends. If you sure you use an MVP in a correct, the Lean way, then I congratulate you, well done and long may it continue.
But if you spend months building an MVP. When you ready to kill yourself or somebody else on your team you finally launch it. Then you see how it converts. You try to find proves it does convert! You find it and plan a second version. Well, in this case, you might want to try this small change in thinking.



Comments

Popular posts from this blog

Fogg Behavior Model

Have you ever wondered why you do certain things? Why are some behaviors easy and joy to do while other not so? And your customers - have you ever struggled to understand their behavior?
BJ Fogg, from Stanford University, has created simple and powerful behavioral model for persuasive product design.


Product Vision: an elevator pitch for your product

On this blog, I write a lot about making data-driven decisions. But what if you just starting to think about your product? You have a vague idea and nothing more. No point to go for prototyping or even talking to customers as you don't know yet who to talk to and what to talk about. In such situation - start from creating a product vision.

7 steps of Product Discovery

Before building a product - how do you know what product to build? While building a product - how do you know what features are the most valuable? After you've built a product - how do you know if to tune stuff or add a new one?