MVP (Minimum Viable Product)

Quality / Updated / COI

Quality

Reviewed

Updated

02/12/2026

Source

Citations & Trust

COI

none

TL;DR

A minimum viable product is the smallest version of a product that can test a core hypothesis with real users and measurable learning.

Definition

An MVP is built to validate the riskiest assumptions with minimal time and resources, focusing on learning rather than completeness. It should deliver enough value to generate user feedback or behavioral data while avoiding unnecessary features. The concept guides scope, experiment design, and success metrics so teams can decide to persevere, pivot, or stop.

Decision impact

• Determines which hypothesis is most critical to test before scaling investment.
• Shapes scope and timeline by prioritizing learning over polish or feature breadth.
• Clarifies success metrics that indicate whether to iterate, pivot, or shut down.

Key takeaways

• Define the exact learning goal before writing requirements or building features.
• Deliver just enough value to get real user behavior, not only opinions.
• Measure outcomes tied to the hypothesis, such as activation or retention.
• Iterate quickly and document what was learned for the next decision.
• Keep quality high for the core experience even if the surface is narrow.

Misconceptions

• An MVP is not a low-quality product; it is a focused learning tool.
• MVP does not mean shipping everything in beta; it means testing the riskiest part.
• Building more features does not reduce risk if the core assumption is untested.

Worked example

A team believes small retailers will pay for automated reorder alerts. They build a lightweight dashboard that pulls sales from a spreadsheet and sends simple email alerts. Only three features are included: upload sales data, set a threshold, and receive alerts. After a two-week pilot, they track whether store owners act on alerts and agree to continue paying, which informs whether the hypothesis is valid.

Citations & Trust

• Entrepreneurship (OpenStax)