@justjimmy, as for my understanding of what MVP is — there actually needs to be an actual functioning product... although, Eric himself does mention in his 'Lean Startup book' to products that qualify under the MVP title with just a video (Dropbox) and a Concierge service (don't remember the product)... I do find it weird that he mentions those as qualifying, since they really just validate the business model.
One of his (Eric) simplest definitions for a MVP was a product that could easily go through a full cycle in the lean.feedback loop: https://skitch.com/vince.baskerville/gixq3/mvp-feedback-loop which should/hopefully help distill what customers want & thus actually pay for.
Validation is exactly what you're seeking, especially in the earlier phases of the learn startup / customer development process. The whole point is to get validated learning as early as possible, and eliminate waste, where "waste" is "building something nobody wants."
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-...
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.
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.
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.