Re:The Death of the MVP (Minimum Viable Product) in Competit...
by stcredzero on Thursday January 05, 2012 @03:01PM
(#3430229)
What "viable" means is heavily context driven.
TLDR: In established markets, viable != minimal.
Re:The Death of the MVP (Minimum Viable Product) in Competit...
by mindcrime on Thursday January 05, 2012 @03:55PM
(#3430474)
I think the "minimal" needs to be looked as as "relative to what you could conceivably build" not as "relative to the market." You always want to build the minimal thing you can, that enables you to get the validated learning that you're after. It's just that if there's an established market and existing players, you probably have to build up to that bar, in order to learn about the bit you intend to do differently.
Or something like that... :-)
Re:The Death of the MVP (Minimum Viable Product) in Competit...
by r00fus on Thursday January 05, 2012 @07:48PM
(#3431382)
> TLDR: In established markets, viable != minimal.
So it's not possible to target a niche with a specialized product that only has 20% of the competition's features, but does those 20% properly for that niche?
Re:The Death of the MVP (Minimum Viable Product) in Competit...
by stcredzero on Thursday January 05, 2012 @11:29PM
(#3431972)
It's still possible. What I mean, is don't expect to be able to get away with something as skimpy as you would in a totally new market.
Re:The Death of the MVP (Minimum Viable Product) in Competit...
by Idhackthat on Thursday January 05, 2012 @03:09PM
(#3430265)
Agreed.
Re:The Death of the MVP (Minimum Viable Product) in Competit...
by thesash on Thursday January 05, 2012 @03:13PM
(#3430280)
100% agree that viable is context driven, but I kind of disagree with your example. If you want to compete with an established player, focus on the differentiating factor that you think is game-changing rather than competing on features, otherwise you'll never win. The early adopters that you want to court will be excited by what's different, not by a clone of something that already exists. By the time the product is ready for the prime time it will need those features, but by then the bleeding edge early adopters will have moved on to the next new thing.
However, in cases like healthcare or finance, or certain B2B applications, viable may entail a much more mature product.
Re:The Death of the MVP (Minimum Viable Product) in Competit...
by mindcrime on Thursday January 05, 2012 @03:52PM
(#3430465)
If you want to compete with an established player, focus on the differentiating factor that you think is game-changing rather than competing on features, otherwise you'll never win
"Never" is an awfully strong statement, but I mostly agree with that sentiment. I see this as orthogonal to the point I was originally trying to make though. My example was probably to hastily constructed and may not have been very clear.
Absolutely, but I'll add this posit: What "viable" means is heavily context driven. If the goal is to learn about whether or not your specific take on things is valid, then what your MVP will need to look like will depend on the kind of market your pursuing, whether or not their are already existing players in your space, how radically different your approach is, etc.
IOW... if you wanted to launch an MVP of a "Facebook Killer" and the "secret sauce" was something, like, oh... some gamification thing... badges or accomplishments related to making new friends, let's say. That's enough like Facebook (or g+, etc.) that the expectation for a potential user would be based around Facebook... your "secret sauce" is only an incremental improvement, so you'd almost have to roll out something as feature rich and visually polished as Facebook, in order to find out if you can compete. That sucks, but one that's why there are both pluses and minuses to entering an established market with an incremental improvement. :-)
Now if your "secret sauce" is something world-changing and totally new, like say, "automatic Frombleglizzits when you Gwizztickum" (whatever that is), then you may ONLY need to build enough to make people understand what "automatic Frombleglizzits when you Gwizztickum" is, and then you can find out if that's compelling to them or not, in isolation. If it turns out it isn't, you would have wasted a tremendous amount of time building a complete Facebook clone just to find that out. You have more uncertainty in this case, but this is exactly where the Lean Startup approach helps... eliminating waste in the face of extreme uncertainty.
good news: no one knows who you are when you launch, so you have nothing to lose.
Exactly.
Unfortunately I think what we're seeing is the lean startup backlash where people use the terms but don't really take the time to understand what they mean.
Absolutely.