News for hackers. Stuff that matters.
Re:Why is your Minimal Viable Product (MVP) really just a PoS by mindcrime on Monday January 02, 2012 @05:59PM (#3417766)
A fairly common definition of "MVP" is something along the lines of "The least you can build to get validated learning." Depending on the situation, it's entirely possible what wifeframe sketches might be an early MVP.

It's also important to remember that this "lean startup" / "customer development" stuff is meant to be an iterative process. Your MVP today might not be the same as your MVP a month from now, or a year from now.

Edit: from Eric Ries himself[1]:

First, a definition: the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.

[1]: http://www.startuplessonslearned.com/2009/08/minimum-viable-...

Re:Why is your Minimal Viable Product (MVP) really just a PoS by gfodor on Monday January 02, 2012 @08:59PM (#3418295)
The devil is in the details. There is no way to know for sure what level of features or polish is truly going to yield unbiased results. It could be that if you were to add that 11th feature, you'd have hit the sweet spot where the product clicks for the consumer. The catch is that there's really no good way to know if it was the 11th or 12th feature that was necessary for you to get there. If your initial MVP with only 10 features fails, how do you know to plug in the 11th or just throw in the towel on that idea altogether?

My biggest beef with the lean startup philosophy is it seems to encourage engineers away from working on deep, hard problems for a long time. It's all too easy to release something basic too early, see it inevitably "fail", and decide to "pivot" based upon this. I feel this is often a symptom of a deeper disease: either not having courage in your convictions or not building something that you could see yourself (or someone you know) using regularly. In short: in creative endeavors it is sometimes healthy to have bias in your views based upon intuition and not direct evidence ("I don't care what the A/B test said, we're going with this idea anyway") because sometimes this intuition can lead you down corners that break you out of local minima up to another plateau.

Re:Why is your Minimal Viable Product (MVP) really just a PoS by mindcrime on Monday January 02, 2012 @10:26PM (#3418488)
My biggest beef with the lean startup philosophy is it seems to encourage engineers away from working on deep, hard problems for a long time.

But it doesn't. If the result of working a deep, hard problem is a solution that the world obviously needs, then the LS methodology does not push doing "MVPs" or whatever. So if you're working on a cure for cancer, or a cheap, clean, renewable energy source, you wouldn't be following this model in the first place. The whole "lean startup" / "customer development" approach is meant for dealing with case of extreme uncertainty, and especially in regards to market/customer knowledge.

It's all too easy to release something basic too early, see it inevitably "fail", and decide to "pivot" based upon this.

Anybody who does that doesn't understand the Lean Startup approach, and isn't doing it right. Every change isn't a "pivot" and you don't go pivoting at arbitrary points just because of an isolated bit of negative feedback. The idea is to find a market for the original idea, as conceived, and pivot only if a market cannot be found (or created) for that.

I feel this is often a symptom of a deeper disease: either not having courage in your convictions or not building something that you could see yourself (or someone you know) using regularly. In short: in creative endeavors it is sometimes healthy to have bias in your views based upon intuition and not direct evidence ("I don't care what the A/B test said, we're going with this idea anyway") because sometimes this intuition can lead you down corners that break you out of local minima up to another plateau.

Agreed... there is a place for vision and intuition sometimes. Unfortunately there's no easy way to know when your intuition is actually leading somewhere. It's a battle we all face.

Re:Why is your Minimal Viable Product (MVP) really just a PoS by sn0wBuM on Monday January 02, 2012 @09:22PM (#3418346)
I think it is easy to confuse market research and product research with the MVP. I don't even quite know the difference according to Eric's definition.

What seems to make sense to me is to simply follow the name. It is the minimum work for a viable product. A splash screen is not a product. A video is not a product. A wireframe is not the product (unless it contains the minimum form of the product). Thus, all of these are not MVPs.

Determining if something is a product should be easy. Determining what is minimum but still viable is much harder.