News for hackers. Stuff that matters.
Re:M.V.P., not M.V.P.O.S. by mbesto on Monday November 18, 2013 @12:18PM (#6755414)
> Otherwise, you're missing the entire point of the M.V.P. in the first place - to iterate quickly on small features based on customer feedback and measurable data.

The entire point of an MVP is validation. In my opinion validation is attained when someone (i.e. a user/customer) has enough energy to respond or give feedback. Customer development comes next (feedback, measure, iterate, etc).

Re:M.V.P., not M.V.P.O.S. by morganb180 on Monday November 18, 2013 @12:33PM (#6755535)
Tough to get valid validation when the product your shipping doesn't solve the need for the end user due to its MVP-ness. If you deliver crap, it's hard to separate the feedback of "this is crap because it's missing xyz feature or looks ugly" vs. "this is crap because it doesn't solve a need."

I've found that people have a hard time separating the two in interviews.