The MVP was a great idea that got misused. "Minimum viable product" was meant to be the smallest experiment that tests a hypothesis. In practice it became an excuse to ship something broken and call it strategy. The minimum lovable product — MLP — is the correction: the smallest release that people actually want to use, not just tolerate. Knowing which one you need is a scoping decision, not a philosophy.
The difference in one line
An MVP asks will they use it at all? An MLP asks will they love the part we built? The MVP tests demand with the roughest possible artifact. The MLP narrows scope but polishes what remains until it's genuinely good.
Both are about doing less. They disagree on where the "less" goes — fewer features versus rougher features.
Why the bar has risen
When users had few alternatives, a rough MVP could win on novelty. Today almost every category is crowded, and people judge a new product against the polished tools they already use. A janky first impression doesn't read as "early" — it reads as "not for me," and they don't come back. In a saturated market, lovability is the viability test.
When an MVP is still right
Ship a true MVP when the core question is demand, not quality:
- You're genuinely unsure anyone wants this at all.
- The audience is early adopters who tolerate rough edges for access.
- You can learn what you need from a small, forgiving group.
- Speed to a signal matters more than the strength of the signal.
Here, spending weeks polishing something nobody wants is the expensive mistake.
When to reach for an MLP
Choose an MLP when demand is fairly clear but the market is competitive:
- Users have real alternatives and will compare you to them.
- Your differentiation is the experience — feel, speed, design.
- First impressions are hard to reverse.
- Word of mouth depends on delight, not just function.
Scope narrow, finish deep
The trap with "lovable" is treating it as license to add features. It's the opposite. Pick fewer things and finish them completely. One workflow that feels effortless beats five that feel unfinished. Cut scope until what's left can be genuinely good, then make it good.
Decide, then commit
Write down the one question your launch must answer. If it's do people want this, ship an MVP and don't over-invest. If it's will people switch to us, ship an MLP and make the core loop delightful. The failure mode is building an MVP's worth of polish across an MLP's worth of features — half-finished everywhere, lovable nowhere.
At Doktouri we scope launches around the one question that matters and finish what we ship. If you're planning a first release, let's talk.
Originally published on the Doktouri Agency blog. We build web, mobile, SaaS, and AI products — let's talk.
Top comments (0)