Eric Ries-Building the Minimum Viable Product

Heh - What if you're naturally lean and you think '2' is the right number of features. I can't make a MVP with quarter of a feature ;)

And yes, this is a joke - I get the advice is golden for inexperienced designers.

One thought that would be great to expand on - What are the realities involved with fall-off rates for customers who get your app (or any product), deem it lacking, and thus file you under 'useless' and keep you there, even when you address their concerns later using an iterative apporach on top of an MVP?

I can see some possible answers like: "It doesn't matter - You will lose them, but new users will come, and they'll evangelise rather than abandon like the early users did" - It would just be great to show evidence so folks can wrap their head around it.

My issue with the MVP is that it could give room for others to pick up the idea, improve on it and claim ownership

Very Informative Video

Just be mindful of your business context: how likely will you get early clients feedback and how likely is it that they will agree to engage with the next iteration if they did not like the first one? If your idea is really a strong innovation with a great value potential for your clients, they will likely be willing to get early yet maybe not lovely versions of your product. If your product is a widely used concept with not fundamental value increment, it s more tricky to get customers to try it, get feedback and get them to try next iteration. They way you ll get your feedback needs to be defined before you build your MVP, as

DAVI BRAGA

My first job was at a company that had released a less-than-viable product, and hoped the new hires could fix it.
They are now the largest software company in Oregon, so they might have done something right.
Except that they got bought, so maybe they didn't