I want to start this new year writing an article to explain something that maybe is not clear to all of us: the difference between a Minimum Viable Product (MVP) and Minimum Marketable Feature (MMF).

Have you ever watched "Back to the Future"? Well, an MVP of that time machine would be a cardboard box with some blinking lights that lets you test if people are interested in time travel. An MMF would be the DeLorean - even though with no customization of colors, lights, doors etc.- but that actually gets you to the 1950s without accidentally erasing your parents from existence.

Minimum Viable Product

MVPs are early scientific experiments, they are the scrappy, bare-bones version of our product. Here it’s all about figuring out if a problem exists in a defined market, and then whether our solution we would realize could fit the mark.

Before we build anything, we must "Start with Why" (let me quote Simon Sinek here), we must understand the problem we are solving: an MVP is laser-focused on the problem. Forget accessories, colored buttons etc, we just need keep the features bare-bones, and to focus on what really matters: the simplest way to prove our hypothesis of the solution to the problem.

the audience of an MVP are early adopters. They understand that perfection isn't the goal - innovation is. Our MVP doesn’t have to be perfect. It just has to be enough to test your idea and get feedback.

Minimum Marketable Feature

The MVP is where we learn fast and test assumptions. It’s built for early adopters with minimal, experimental features. The MMF, on the other hand, is all about delivering value and marketability. It’s aimed at a broader user base and is polished, complete, and ready to impress. While the MVP validates hypotheses, the MMF enhances the product’s usability and appeal.

The transition from MVP to MMF is a progression based on validated learning. Each feature added in the MMF should address specific needs discovered during the MVP stage. Success lies in understanding when to stay in MVP mode and when to transition to MMF: if we release too early with insufficient features, we risk losing user trust... But if we add too many features, we might waste resources on capabilities nobody wants.

By the way, if you want to know more about MVP, I suggest you to read the book The Lean Startup by Eric Ries