Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The one thing people seem to forget: MVPs are supposed to be experiments. You do an MVP to figure out whether it's worth your time to build a product for a particular market (i.e. whether there is "product-market fit"), or whether you should pivot to something else. You make them minimal so you can afford to do more of them, because it's unlikely your first one will work. You make them viable because, if they aren't, your experiment won't tell you anything (people won't use it, even if they need what it does.)

If you already know your product is something people want (e.g. something a bank would just give you a business loan for), you obviously don't need to do an MVP, because there's already product-market fit. Starting a pizzeria? Front-load your investment and make a really great pizzeria; buy huge ovens, etc.

If there's literally nobody serving your market, such that it's unclear whether it's even a "need" or not—please don't spend years building the perfect solution to the "problem." Find out if it's a problem first. Build a prototype. Show it to people. Get them to say they're willing to pay you for it. That's what an MVP is.

(And, as soon as you've found your product-market fit, and decided which product you're going to build? Stop thinking of that product as an MVP. It's a real product now: make it good.)



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: