MVP usually means Minimum Viable Product: build small, launch fast, get feedback. That makes sense. But sometimes “minimum” becomes the wrong mindset. Imagine the Mona Lisa as an MVP: a few rough lines, a basic face, no mystery, no soul. Maybe it would be “viable,” but would it be valuable? I’m not saying we should chase perfection. But maybe the better question is:
What is the smallest version that still feels truly valuable?
MVP usually means Minimum Viable Product.
Build the smallest version, launch fast, get feedback, improve.
And I agree with the idea of testing early.
But here is another thought:
What if Leonardo da Vinci had presented the Mona Lisa as an MVP?
A few rough lines.
A simple face.
No mystery in the smile.
No depth.
No soul.
Technically, it might be “viable.”
But would it be valuable?
In product development, speed matters.
Feedback matters.
But value matters more.
Maybe the real goal should not always be Minimum Viable Product.
Maybe we should aim for Maximum Valuable Product.
Not perfect.
Not overbuilt.
But meaningful enough that users can feel the value from the first experience.
Because users do not fall in love with “minimum.”
They fall in love with something that feels worth their time.