Only you know your MVP, ask yourself why you want to do

I'm working on a product and I've tried to ask other people what to do with something, how to do it better. Should this appear in MVP, and how should that be designed in MVP?

But in the end, you need to go back and email list ask yourself more, only you know what your product value proposition is. What will the future look like. What pain points do you want to help customers solve? What value does it bring to them.

I remember when I made the first product, I didn't think about MVP. The little friends were not aware of it either. At that time, there were plenty of resources, so they did it.

When making the second product, because resources are really scarce, not only there are few people, but also fast results are required.

So, I had to think about MVP and adjust in practice.

3. The last words

There is a saying: "Don't limit yourself."

Well, I feel like everything is the same, there can't be limits. Let's not put limits on MVP either.

Times are changing, and MVPs are evolving.

Finally, let's summarize the MVP.

First: using MVP is not the purpose. The goal is to test your hypothesis in the least amount of time, and then do it in a planned way.

Second: MVP may not be a product that allows users to click with the mouse. Any object that can clearly explain the value of the product can become an MVP (to achieve verifiable purposes). Such as polling research, crowdfunding methods, fake products that look like real products (such as the case of "Zappos' MVP" above).

Third: The MVP needs to embody the unique value proposition of the product. Don't do it just because he's an MVP now (as if he's a child and don't care about his long-term growth value). who is it? What pain point does it solve? Where is its future heading? All need attention.