Seems to me there is a continuum of vaporware-->MVP-->real product, and the art of it is to know where on that line to start. As a repeat tech co-founder, I ea

Seems to me there is a continuum of vaporware-->MVP-->real product, and the art of it is to know where on that line to start. As a repeat tech co-founder, I easily fall into the trap of being a perfectionist & a complete-ist, always wanting to add one more feature or refactor one more poorly designed aspect of the project. So I appreciate this article as it pulls in the other direction. However I think doing what he calls MVT's -- basically sub-standard, feature-poor, non-scalable MVP's -- can lead you astray, or simply fail to properly test the hypotheses in question. In the end it comes down to judgement and experience. I've taught myself to put time-to-market at the top of my list of priorities, but it is still a struggle between wanting to 'get it right' vs missing the opportunity or chasing the wrong assumptions.