minimum-lovable-product-mlp

name	Minimum Lovable Product (MLP)
description	In an era where AI lowers the cost of building software, viability is obsolete. The differentiator is joy and emotional connection. Prioritize "Wow" over "Aha"—brand is product interaction.

The Minimum Lovable Product (MLP)

"Viability is left back in 2010s. Now it's minimal lovable product." — Elena Verna

What It Is

A development standard that prioritizes emotional connection, brand feel, and "magic" over simple functional viability. In an era where AI lowers the cost of building software, the differentiator becomes the joy of use.

When To Use

• Entering a crowded market with low barriers to entry
• Competitors offer similar utility
• When "MVP market tests" yield indifference, not feedback
• Building consumer or prosumer products

MVP vs. MLP

         MVP (2010s)                    MLP (Now)
         
    ✓ Does it work?                ✓ Does it delight?
    ✓ Is it viable?                ✓ Is it lovable?
    ✓ Aha moment                   ✓ Wow moment
    ✓ Understand value             ✓ Feel the magic
         
    Result: "It's okay"            Result: "I have to share this!"

Core Principles

1. Brand is Product Interaction

Do not separate brand marketing from product design. Every UI interaction must convey the brand's personality.

2. Prioritize "Wow" Over "Aha"

The goal is an immediate feeling of "I can't believe this is possible" (Wow), not just understanding value (Aha).

3. Fix "Unlovable" Bugs Immediately

If a feature works but feels clunky or lifeless, treat it as a P0 bug. Stop the line to fix the "vibe."

4. Designers as Early Hires

Hire high-agency designers earlier than usual to ensure the emotional layer is built alongside the functional layer.

How To Apply

STEP 1: Define Your "Lovable" Standard
└── What makes users share this?
└── What creates word-of-mouth?

STEP 2: Audit for Vibes
└── Does every interaction feel magical?
└── Is the personality consistent?

STEP 3: Create "Lovable Veto"
└── Anyone can flag feature as "not lovable"
└── Team drops sprint to fix it immediately

STEP 4: Measure Emotional Response
└── NPS is not enough
└── Look for unprompted shares and social posts

Common Mistakes

❌ Shipping a dry, utilitarian MVP that yields indifference

❌ Separating "brand" from "product" (two different teams)

❌ Treating emotional polish as a post-PMF luxury

Real-World Example

Lovable's internal culture where anyone can flag a feature as "not lovable," causing the team to drop sprints to fix the interaction immediately.

---

Source: Elena Verna, Head of Growth at Lovable, Lenny's Podcast