Minimum Lovable Product

RR
Ryan Rutan

Minimum Lovable Product

Minimum lovable product (MLP) is an evolution of MVP that emphasizes shipping something users love at launch, not just the bare minimum that works. It favors a polished, emotionally resonant, focused product even at the cost of breadth, arguing that in crowded markets a working-but-uninspiring MVP produces no traction even when the underlying value proposition is sound. The term was popularized in the late 2010s by Henrik Kniberg (Spotify, "The Skateboard, not the Wheel" analogy) and Jiaona Zhang (writing in product-leadership communities like Reforge and Lenny's Newsletter).

The MLP critique of classical MVP runs like this: Eric Ries's MVP was designed for the lean-startup era of 2010-ish, when product expectations were lower and a clunky-but-functional product could earn enough attention to learn from. By the 2020s, every category had become crowded and user expectations had risen, so a literal "minimum" product looked broken next to the polished competitor in the next browser tab, no matter how clever the underlying validation. Henrik Kniberg's widely-circulated drawing illustrates the difference: an MVP built incrementally as wheel → axle → chassis → car is unusable at each step until the last. A skateboard → scooter → bicycle → motorcycle → car path is usable and lovable at every step, even though the first step is nothing like the final product. The MLP is the skateboard, not the wheel: small, focused, and delightful at its limited scope. Famous examples often cited: Linear launched with a tiny feature set but extreme polish in keyboard interactions and speed; Superhuman launched with limited functionality but felt premium from the first second; Notion launched as a minimalist doc tool with deep focus on typography and feel. The trade-off: building lovable takes more design and engineering investment per feature, which means an MLP usually does fewer things than an MVP would.

Ryan's Take

The MLP versus MVP debate is mostly a fight between "ship something embarrassing fast" (Ries) and "ship something polished but tiny" (Kniberg and the modern product-design community). Both are right in different contexts. If you're in an unproven category with patient early adopters, a janky MVP can earn attention. If you're entering a crowded category with high user expectations, an MVP looks broken and an MLP is the only shot. Pick based on your market, not based on which book you read most recently. The actual question is "what's the smallest thing my target user would actually use and tell a friend about," and the answer is almost never a half-finished MVP in 2026.

What founders get wrong: Treating MLP as permission to ship more features. The "lovable" in MLP modifies the quality of a small surface area, not the scope. An MLP is still minimum; the discipline is that the small thing it does, it does beautifully. A product that tries to be lovable across 20 features ends up being a half-baked everything-tool.

Related: MVP · Product Market Fit · Product Strategy · Product Discovery · User Experience

FAQ

What is a minimum lovable product?
An evolution of MVP that emphasizes shipping something users actually love at launch (a polished, focused, emotionally resonant product, even at the cost of breadth) rather than the bare minimum that technically works. Popularized by Henrik Kniberg, Jiaona Zhang, and the modern product-design community.

What is the difference between MVP and MLP?
MVP (Eric Ries) emphasizes the smallest thing that validates a hypothesis, often unpolished. MLP emphasizes a small but lovable surface area that meets modern user expectations, even at the cost of doing fewer things. Both are minimum; MLP shifts the variable from "fastest to ship" to "smallest thing worth loving."

When should I build an MLP instead of an MVP?
In crowded markets with high user expectations, where a janky product looks broken next to polished competitors and produces no traction. In unproven categories with patient early adopters, a classical MVP can still earn attention. Pick based on your market, not the framework's reputation.

Find this article helpful?

This is just a small sample! Register to unlock our in-depth courses, hundreds of video courses, and a library of playbooks and articles to grow your startup fast. Let us Let us show you!

OR

GoogleLinkedInFacebookX/Twitter

Submission confirms agreement to our Terms of Service and Privacy Policy.