> An example of too much minimalism would be failing to implement UI pagination and your UI falling over with more than 20 objects, because you didn’t think about the use case. Maybe you haven’t thought about scale-out or upgrades or you can install on only one operating system. A serious buyer can sniff out this incompleteness and won’t take you seriously, and only serious domain experience can fill in these gaps. You can’t expect your buyer to be like “hey, nice try with this prototype but I can tell this won’t scale to more than 20 objects”. They are looking to you to be the expert.
IME this part is completely wrong, unless it's defining "serious buyer" in such a way that most of your market isn't one.
> Time is short, funding is short (especially if you are running on your own money), and you don’t want to waste time.
> Your company shouldn’t be in search of a business model, you should know what you need to build. Wait until you see the exact right thing, because you are about to put too much of your lifeforce into it, and if you don’t, you have a much harder road ahead. You want to know it will work, and this requires cultivated instinct. When the time is right and you know enough, that’s when you decide to have a product.
Ok so what is the author advocating doing until then? Sitting around twiddling your thumbs until inspiration strikes?
The whole point of the MVP is: build just enough to find out whether this is a viable business or not. And nothing in the article seems to be contrary to that. It's a whole lot of words but the only advice seems to be to have better instincts (how?) and just make a better product bro.
IME this part is completely wrong, unless it's defining "serious buyer" in such a way that most of your market isn't one.
> Time is short, funding is short (especially if you are running on your own money), and you don’t want to waste time.
> Your company shouldn’t be in search of a business model, you should know what you need to build. Wait until you see the exact right thing, because you are about to put too much of your lifeforce into it, and if you don’t, you have a much harder road ahead. You want to know it will work, and this requires cultivated instinct. When the time is right and you know enough, that’s when you decide to have a product.
Ok so what is the author advocating doing until then? Sitting around twiddling your thumbs until inspiration strikes?
The whole point of the MVP is: build just enough to find out whether this is a viable business or not. And nothing in the article seems to be contrary to that. It's a whole lot of words but the only advice seems to be to have better instincts (how?) and just make a better product bro.