Minimum Viable Product (MVP)

The minimum viable product is built to learn, not to showcase full features. It focuses on the minimum set of functionality needed to validate whether customers experience the intended value. A well-designed MVP defines success criteria, collects feedback, and informs whether to iterate, pivot, or scale.

It determines the scope of the first release and the learning goals. It guides what metrics and feedback to collect from early users. It influences whether the team should iterate, pivot, or invest further.

• It determines the scope of the first release and the learning goals.
• It guides what metrics and feedback to collect from early users.
• It influences whether the team should iterate, pivot, or invest further.

• Build only what is needed to test the core hypothesis.
• Define success metrics before launching the MVP.
• Use real user behavior as the primary feedback signal.
• Keep costs low to preserve runway for learning cycles.
• Document what was learned and what will change next.

A team building a meal-planning app starts with a simple web form that generates a weekly menu based on dietary preferences. They track completion rate and repeat usage to test value. Feedback shows users want grocery integration, but only after menu quality improves. The team iterates on the core algorithm before adding new features, keeping the MVP focused on learning.

• An MVP is not a low-quality product; it is a focused test.
• An MVP is not a prototype with no users; it must deliver value.
• Shipping an MVP without clear learning goals wastes time.