Iren Korkishko — there is no doubt that launching something faster with an emphasis on seeking…
But that approach still doesn’t guarantee success and still begs the question: “How do you or your clients decide what goes in the MVP?”
Iren Korkishko — there is no doubt that launching something faster with an emphasis on seeking customer validation is better than the waterfall alternative of launching a “complete and perfect” product a year later.
But that approach still doesn’t guarantee success and still begs the question: “How do you or your clients decide what goes in the MVP?”
I briefly scanned some of your articles and didn’t see how, other that your clients telling you what they want in the MVP, you help them decide what is the minimum feature set?
The point of this article is that too many MVPs simply miss the mark completely because they are guesses. Your clients aren’t the customer and often don’t know what they want. Customers too are starting to get MVP fatigue — they aren’t testers of half-baked solutions and don’t want to be…
This isn’t MVP abuse, just current reality. The solution is to level up the game for MVP definition. You can get to a lot of these goals with assembling and testing an offer before building a MVP.
The Dropbox case-study is an example of offer testing at work vs MVP testing.
Cheers.