You're missing the forest for the trees.<p>The heart of "do less" and "minimum viable product" isn't to do a crappy job or to have a minimalist product.  The point is to relentlessly prune your feature set and relentlessly prune your features so that you're solving real problems and offering the most value per feature.<p>Prune your feature.  If you cut two less use-cases from your feature's spec, is it still meeting user's -real- needs?  Is it easier to use now because it's less complex?<p>Prune your featureset.  Is that feature something that meets real users needs?  Even an HN hero (patio11) had this issue recently when he launched a feature and had all of 2 customers use it.<p>Get validation.  Don't answer these questions by intuition alone.  Get customer feedback, hear what they are saying, and do root cause analysis on why they have those complaints.  Make sure after you've launched a feature that it's actually solving customer's problems.<p>Tighten your feedback loop.  Living in a black hole for weeks at a time lowers the chance that your feature will actually solve people's problems.  Have a feature that will take weeks to build?  What's the smallest subset of that feature you can launch that will tell you if it is actually solving real issues?  Even if you have to launch that feature internally or to a small set of users, you need to figure out if you're on the right track as soon and as often as possible.<p>Do less isn't really about having less features.  It's a strategy for satisfying the most customer needs for dollar.  You do this by seeing a problem, proposing a solution, and building the least you can to verify that your solution is correct.