Got it, and that sounds perfectly reasonable. I'd describe it entirely differently from an MVP, but it is reasonable to make a demo to judge reactions and see where points of confusion are in how the product will work.

As well, there are two large categories of MVPs, low fidelity and high fidelity (https://www.robotmascot.co.uk/18-types-of-minimum-viable-pro...), and subtypes within that.

What I did was a "fake door" MVP, as the article states. It is not necessarily intended for directly measuring sales but whether its worth my time to build it in the first place. Having over a thousand sign-ups now, it validates that I should indeed spend my time on it.

Then, I would make a high fidelity one, a "one feature" MVP as the article calls it, which would cut the product down to its essence and see if it can still solve a specific problem, and whether people would still pay for only one feature. I am doing this now with a mobile app instead of web/desktop app as the reduced screen space forces me to think about the problem of time block productivity from its essence.

Perhaps your definitions of MVP are different than others, which is perfectly fine. There are others I've seen over the years like simple, lovable, complete (products), and so on (https://news.ycombinator.com/item?id=22955085).

Yeah, I think we are arguing semantics. For me, not being an entrepreneur, the "viable product" portion of MVP seems like it is a useful distinction. In your original post, when you said that you had an MVP that just consisted of a video, I interpreted it as a form of fraud. (i.e. "I sold customers a product that doesn't exist, using a video to fool them.")

This terminology fuzziness is a direct result of SEO. "MVP" = Good Thing in entrepreneurial circles, so things that are not viable products are labeled as such because they want to be associated with that keyword.

100%. satvikpendem is doing wordplay. A video of a nonexistent piece of software is a useful tool, but a viable product it is not.

That he's denying this proves your point.

I don't think so. Look at the other comments replying to my thread. The definition of MVP can mean finding the fastest way to validate with the least effort, as Eric Ries is quoted in the other comment. Perhaps at one point MVP did literally mean the smallest usable product but now the product does not necessarily need to be usable, it just has to validate a hypothesis.

Edit: Agree to disagree.

/shrug

> And a WIP can mean something I haven't even started on yet. /s

> You're twisting the meaning of the words in the acronym. I really don't care, but it renders the words meaningless to use them that way.

Again, I'm not sure how to explain that MVP does not literally mean an actual product. It's a tool for hypothesis testing, you don't spend time and energy building out your entire product before you show something to customers, that would be a waste of time and energy. That's why I, and others, define MVP as anything that let's you understand something new about your market and eventually you use that knowledge to make a product.

Should words have shared meanings? Otherwise communication collapses. You promoted a mock-up and got interest to motivate building a product. That's great. Why use misleading words to describe it?

As I've stated in my other comments, the words I used such as MVP are not misleading, or at least, they have multiple meanings, such that those who understand what I meant by MVP were not confused as to its multiple meanings, so the communication was clear enough.