There is a concept called MVP – Minimum Viable Product.

Even though the name kind of says it all, the concept “MINIMUM” – “VIABLE” – “PRODUCT” indicates that there are as few features as possible, it must kind of work and it is a product – most entrepreneurs interpret MVP as the early iteration of a product they want to build. But that is definitely not the case. Let me explain it in more details:

1) MINIMUM VP
An MVP is supposed to demonstrate your core functionality that shows how your product is different from others. And as such focus exclusively on the core mechanism and process of the new solution. If you build a self driving car, it would be perfectly OK to use an old VW beetle that may have no lights and only one seat. But if it is perfectly self steering – you made a great MVP. Try to implement as little features as possible. Every “nice to have” feature destructs unless it is absolutely necessary to show the core idea.

2) M VIABLE P
Be aware that the MVP will only be used by early adopters and need to be seen by investors and other key people. They are typically smart enough to abstract the concept and imagine where you want to take it. It just needs to show the core feature in a very solid way. It need to work over and over again. The function needs to be robust enough that anybody can envision you build the whole concept in a beautiful way later on. Equally important, let the users experiment with it BEFORE it is ready. You will want to learn as much as possible from those users to build the final product after their feedback. Redoing a product is not only much harder but a rather “ready” product may mislead users to a behavior they may not be able to articulate their pain – rather leave it open in an MVP.

3) MV PRODUCT
Make sure that you have a well thought out business model that is actually the disrupting part of your solution. EVERY business model is reflected in the MVP. If the business model is lame, your MVP will not be too catchy wither. Make the PRODUCT reflect your business model.