2 min read

A common validation techniques is the MVP.

This stands for Minimum Viable Product — the minimally viable version of your product that you can put in front of users, and observe their interaction.

But, so many founders, product owners, and agile teams have defined this term that it suffers from overdefinition — nobody knows what it means anymore. So let’s try to make sense of the concept.

1. What is minimum, viable, and a product?

1. Minimum means the least amount of effort/technological complexity/infrastructure required.
2. Viability could mean that the product works for the user, it solves users’ needs, and therefore accomplishes a degree of PMF — product-market fit.
3. Finally, it has to be a product — not a good one, just has to be one. Which means users have to want it, purchase it, and find reason to use it.

When put together, it means if even your early adopters don’t love your product, you haven’t reached the minimum aspect, and certainly not the minimum viable aspect.

That’s why asking for an MVP is a tall order before the delivery stage has begun. It’s akin to having the full product out.

2. Should I have an MVP?

MVPs as a concept was developed when first-movers in niche markets was a common occurrence.

Now, industries are more or less saturated with at least some company with some level of product that targets the use case.

Putting an MVP in front of a customer in 2022, they are likely aware of similar products to judge yours by. What that means for you is that the standard of an MVP has risen dramatically over time. That’s why shooting for an MVP right off the bat is often a bad idea, and why the catch-all term “MVP” often leaves room for questioning.

3. MVP as a Mindset