An Easy Way to Make Minimum Viable Product (MVP) Totally Not Viable
5 minute read
The Minimum Viable Product (MVP) concept has taken off over the past few years, and indeed, its heart is in the right place. MVP encourages product managers to scope features and functionality carefully so that customer needs are satisfied at every stage of development — not just in a sweeping finale at the end of development.
It’s a great way to shorten time-to-value and test new market concepts before committing. Zappos, for example, started by posting pictures of shoes on the internet without having an inventory — they wanted to quickly test to see whether people would even consider buying shoes without trying them on.
Unfortunately, adhering to MVP won’t guarantee success thanks to one critical caveat: if your product already exists, you have to consider your product’s base state. What can your customers do right now with your product? Failure to take this into consideration can be disastrous.
Here’s what I mean: let’s say the product is your company’s web site. If you’re starting from scratch, a perfectly suitable MVP would be a splash page with one or two sentences about what you do, and some contact information. Customers will be able to find you and communicate with you, and you’ll be providing greater value than without a web presence.
But if you already have a 5000-page site online, that solution is not going to fly. Customers and prospects returning to your site will wonder why it vaporized. If they’re relying on the content or functionality you previously provided, chances are they will not be happy. Confused, they may choose to go elsewhere.
The moral of the story is: in defining the scope of your MVP, take into consideration what your customers can already do, and don’t dare give them less in your next release.