Have you ever learned the idea of ​​MVP, but still don't know how to implement it in actual products? For which functions can be attributed to the MVP, which should not be attributed to the MVP, I don't know how to start? At the beginning, I thought I had understood MVP after email list learning MVP theory, but it was not. On the one hand, in actual work, I always want to make a perfect product at one time and give customers a "wow" feeling. On the other hand, the development time is tight, and there is no time to think about MVP. I just want to quickly sort out a bunch of functions and try to develop them quickly. Until I was in charge of building a 0-1 product myself, I found that I didn't understand MVP, I couldn't apply it flexibly, and I couldn't come to a reasonable conclusion at a critical moment. I deeply felt that "what you have learned on paper will be shallow, and you will never know what you need to do." Today, I want to share with you some of my insights on MVP. Because under the guidance of the MVP model, our products not only have seed customers after half a year, verifying the feasibility of the products, but also won the winning prize in the company's internal competition, which is everyone's recognition and encouragement for our products. This also made me think about what is a feasible MVP in the process of practicing MVP. First, let's take a look at what exactly is MVP in theory?