Minimal Lovable Product

Minimal lovable product is the version of an early release or prototype that is still small and frugal, but includes at least one feature or experience that creates real customer delight rather than merely satisfying technical viability.

Key points

• AWS contrasts minimal lovable product with minimal viable product: viability is not enough if customers are not excited enough to return ^[src-017].
• The first release should include something that makes the customer experience feel worth using, even if the feature is not strictly required for core functionality ^[src-017].
• Minimal lovable products still start small; the point is not a large build, but a focused experiment that can test desirability and value quickly ^[src-017].
• The session connects this to frugality: teams should prototype cheaply, test quickly, and scale only what works ^[src-017].
• Working backwards helps identify what “lovable” should mean by grounding the prototype in a specific customer problem and success metric ^[src-017].

Related entities

• Amazon Web Services — discusses the concept in the working-backwards session

Related concepts

• Working Backwards
• PR FAQ
• Customer Co-Design

Source references

• ^[src-017] AWS Events — “Working Backwards | How to Build Like AWS” (2026-02-24)