📎 Webclip
Don’t Serve Burnt Pizza (And Other Lessons in Building Minimum Lovable Products)
Jiaona Zhang argues that MVPs often test a flawed or weak version of the product, so teams should aim for a minimum lovable product instead. Her method starts with a high-value user problem, then narrows to the few features that deliver real value, delight, and a clear reason to keep using the product.
Reading notes#
- An MVP can miss the real lesson if it only proves that a poor version of the product is unattractive.
- Lovable products require understanding what users value, not just what is functional.
- Start with the user’s why, not the business’s why.
- Separate the problem space from the solution space.
- Listen to users carefully, but do not take their words literally.
- Choose the highest-value problem before entering solution ideation.
- A good test question ends with value for the user, not business logic.
- At Dropbox, Project Harmony solved a basic pain point, but did not reach the richer collaborative experience users actually valued.
- At Airbnb, the team focused on user-centered supply quality in desirable markets, not supply growth in general.
- The minimum in MLP means choosing one or two features that create value instead of spreading effort too thin.
- The Airbnb Plus team shifted from a long hotel-amenity checklist to features that reinforced what people already loved about Airbnb.
- In the host app, the team prioritized the inbox, calendar visibility, and message templates because those solved the most important user problems.
- User misbehavior can reveal what users find most interesting or lovable.
- Pixie dust is the small moment in the product journey that creates surprise, delight, and word of mouth.
- Good pixie dust depends on timing and on fit with a specific audience.
- Beta users are the best group for testing lovable details because they are trusted enough to give honest feedback but not so skeptical that they reject experimentation.
