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

> The whole MVP process presumes you don’t know what you are making for a product, and that is death.

No, the MVP process presumes that you are not omniscient.

Just because you think you know what a customer wants, doesn't mean that anything you make will satisfy the customer. They need to actually get their hands on it, so they can tell you if it works for them. 99% of the time they will be unhappy about something. And that is fine; nothing is ever perfect! But if there is a big expensive time-consuming problem, you won't know that until the customer gets their hands on it, so you don't want to wait long to find those problems.

You want to find those problems as early as possible, so you can fix things early, to reduce the time/cost/complexity of "fixing" things down the line, so your time and money is spent building things right the first time. This reduces cost, speeds up delivery, and improves quality. This concept is called Shift Left.

MVP is intended to get something in the hands of the earliest customers so they can give you feedback. Some people use this just to figure out if they have a market or a product to sell at all, but you don't have to use it that way. You can use as a "minimum customer-acceptable prototype with feedback".



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

Search: