Tag Archive for: MVP

The 7 virtues of idea validation

  1. The absolute very first people you go to, are your potential customers. Listen very carefully what they say.
  2. Never ever fear that anybody can “steal” your idea. This is a myth that seem to never go away under first time entrepreneurs. That fear, by the way, is the no.1 reason why millions of great ideas vanish away and never see the light of day. Don’t bother your future clients with NDAs or other legal confrontation. This makes no sense.
  3. Interview your target audience BEFORE you spend a single penny or minute in prototyping or writing your first lines of code. Everything you do prior to speaking with them is pre-conditioning your thoughts. That bears the risk that you may start arguing with your contact.
  4. Structure the interview around 3 strategically craft questions:
    a) “How would the proposed idea help you?” Let them tell you their possible story, don’t “sell” your idea.
    b) “If you would build it, what would you charge, where would you see a good price point”. Find out what value they see.
    c) “What would you do 9 month later, if I would tell you the product is no longer available. What would be your alternative?” Find out if you have just a nice to have or it would be a serious problem when your idea is not maturing.
  5. Put yourself in a state of “very awake meditation”. Meaning you are hyper carefully listen, you never argue even a tiny bit, and you document not only what they say but also the emotions you noticed. Consider yourself an emotionless AI based Robot. When they don’t get what you say, make a note and trim your presentation.
  6. Don’t ever bother ‘potential customers’ with any type of faceless survey.
  7. Make sure you speak with at least 42 people. That number is important:
    – it has some undocumented statistical value
    – it forces you to find enough potential customers to start with
    – if you find only less than 42, it indicates that it will never warrant a business
    – you get the necessary feedback to decide your MVP functionality
    – it helps you understand how much time you spend to find, reach and talk with your audience – first indication for customer acquisition cost.
    – if you can’t get at least 20 positive feedbacks, continue until you have 20,

This is called idea & first market validation and is a key process in every top notch startup – BEFORE it was a real startup.

Most people just go and run. They fail but fail far later and have a 90% failure rate. Even though every startup entrepreneur today knows, that they ave only a 10% chance to win, they are sloppy right out of the gate :)

I get about 5 questions like that every day. And since I’m rather lazy, I wrote this post :)

Hope it’s helpful.

 

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.