6
12 Comments

Ask IH: What do you think about MVP quality?

I believe Lean Startup. But I'm confused about how I define the MVP of the product every time. For example, how did Stripe validate their business? It's too tough to build API as MVP. In addition, customers often avoid using too minimum products because it looks unsafe and not good design.
Every day, I visit Product Hunt. These products are never MVP. They build totally. What do you think about MVP quality? #ask-ih

on August 3, 2019
  1. 3

    I use to be a person who developed the entire product as the MVP before going live but this approach is not suitable at all. Why?

    • You get burned out quickly. When I use to test products, I always build the entire system before advertising. This is OK at first but within time, you will feel burnt out.
    • They don't have customers. as a person who has gone the same process as you describe, the number of customers I got was not a lot. Some products I tried didn't get any.
    • Having a full product does not mean it will be successful. You don't know if it goes well. If it doesn't then you have spent your time and effect inefficiently.

    After I learned this (the hard way), I start understanding the concept of MVP which should be a lot smaller than products are released on Producthunt. I now make an earlier version (validation product) than an MVP which explain my service first (and get early access users who maybe interested). I believe this process is better because you avoid burning money, effect. First validating to your customers is best.

    I recommend making a validation page which should not take more than a day to make and talk to your target audience.

    1. 1

      Thanks @rashid777

      I totally agree with your idea. And MVP quality is too far from Product Hunt ones. What is the most efficient way to approach your target audience, do you think?

      1. 2

        Yeah, from my experience. Just make a validation page explaining your service and see if they like it.

        1. 1

          I see. Thanks :)

  2. 3

    I think, too many people just consider the M, but not the V and the P. An MVP is a lot more than a buggy demo of what you intend to build. It has to be a viable product! An MVP for a payment processor could mean that it's only live in one country, for one currency and only for credit cards. But to be a viable product, it has to accept payments successfully. That's my criteria for the M in MVP: It should be useful for my first day customers, even if I'd stop adding features on day two.

    1. 2

      Thanks @Stefan22
      I read a similar article you mentioned.

      MVPs are too M and almost never V. Customers see that, and hate it. It might be great for the product team, but it’s bad for customers. And ultimately, what’s bad for customers is bad for the company.

      quoted from I hate MVPs. So do your customers. Make it SLC instead.

      1. 2

        Thanks, interesting article. I haven't seen it before, it was just my own experience. But glad to see I'm not alone on it.

  3. 2

    MVP is just enough to keep the conversation with your users moving forward.

    1. 1

      Exactly. Thanks for your comment.

  4. 2

    Defining an MVP definitely changes now that everyone is thinking that way. Since more people are getting things out earlier in the process, it still has to be differentiated in some way.

    The biggest thing is an MVP has to solve a single, distinct problem. It doesn't have to do a lot of things for a lot of people, but it DOES have to do at least one thing really well.

    1. 2

      Thanks @Zavzen
      MVP should be a single solution for a single problem.