Don’t build a minimum viable product
- Jun 17, 2013
- By admin
- In Uncategorized
- Share on
Don’t get me wrong. I am indeed a fan of fast iterations on product, as professed by the lean startup principle. But, the success of a term, like in the case of ‘Minimum Viable Product’ (MVP), often results in loose interpretations that often go squarely against the original intent. I am afraid the MVP concept is heading there, widely abused by practitioners and preachers alike.
In the earliest stages of your startup,[tweetherder] a product is just about anything that your customer is willing to pay for[/tweetherder].
Some disclaimers here:
1. I’ve not used the word product in its traditional meaning – Something that’s built once, sold/used several times. I am using the word product here to mean a ‘system’ which could be a one or more of the following: Product, Process, Procedure or anything that solves a problem/creates pleasure for a barter.
2. By Payment, I don’t necessarily mean ‘dollars’. Customers could pay by giving their time, doing certain actions, opening their network, paying money etc.
[tweetherder]So when you define your product to be that which gets your customer to engage or react, there are only two outcomes – Engage the way you had expected (or) engage in a way you had not[/tweetherder]. Either way you are making progress. You know a bit more about your customer.
The minimum that you need to do (or code or create) to get a customer engage, need not always be a software product. Often times it should not be. Why?
[tweetherder]Coding is expensive. It’s not minimum[/tweetherder].
Very recently we had a customer who wanted to build a mobile app that discovers certain types of service providers in a radius in real time, so that they could be called in for service. It would have costed them about 2 months and 20,000 $ to get that out in the market. Instead they made an excel sheet of providers, checked their availability twice a day and sent a note to prospective customers everyday morning about possible providers for that day, near their houses.
What just happened? The hypothesis was put to test the very next day, instead of 2 months later and at a cost that is 1/10th of building an app.
So, what did they do? They tested a ‘Minimum viable business’ of which the product (in its traditional meaning) played no role.
It is indeed possible in the case of several startups, to test an idea without the product. Let’s take another example.
ContractIQ was run for most of its last 15 months, out of excel sheets and skype calls with little or no product. Whenever we attempted to build a product, we got ourselves ahead of the need and built something that satisfied our egos than the customer needs. Meanwhile, the customers were happy Skyping us!
So, [tweetherder]before you call us to find a vendor for outsourcing your app development, think if you need to build an app at all[/tweetherder]!
If you still have to, talk to us.