2 ms·

Sam: "Step 1, build something that users love" How does this compare with an MVP approach where you put something out there first and test the market. Then the

Sam: "Step 1, build something that users love" How does this compare with an MVP approach where you put something out there first and test the market. Then there is the issue of runway. With enough time, you can start with an MVP and iterate in private beta until users love it, but in many cases a founder is not going to have that kind of runway. They have just enough resources to put something together, and they're going to have to go out to the market with that and iterate on the fly. Unfortunately, once you do get out there and need to take on all of the other responsibilities, then that's time taken away from building a great product.

napoleond 12y ago
The two concepts are not mutually exclusive. If you target a big enough pain point, your first users will love the product even if it lacks polish. It's also important to remember that MVP != shit. It is the minimum viable product; in the context of the YC motto it's the minimum product that a small, core group of users will love. This is all theoretical on my part, FWIW--I have not successfully built such a thing on my own yet.
bayesianhorse 12y ago
The MVP is a philosophy to get to "something that users love" as fast as possible.