Minimum Viable Product

A minimum viable product, commonly abbreviated MVP, is the simplest version of a new product that allows a team to collect the maximum amount of validated learning about customers with the least amount of effort. Rather than building a fully featured product before testing it on real users, teams release a stripped-down version to learn quickly whether an idea is worth pursuing.

Origins of the term

The phrase “minimum viable product” is generally credited to consultant Frank Robinson, who began using it around 2001 while working with technology companies on product development strategy through his firm SyncDev. Robinson used the term to describe a product with just enough features to satisfy early customers and provide feedback for future development.

Ries and the Lean Startup

The concept reached a much wider audience through entrepreneur Eric Ries, who built on methods he developed with Steve Blank and popularized the MVP in his 2011 book The Lean Startup. Ries framed the MVP as the centerpiece of a build-measure-learn feedback loop: build a minimal version, measure how customers actually respond, and use that data to learn whether to persevere with the idea or pivot toward something else.

Famous MVP examples

Several well-known startups are frequently cited as MVP success stories. Dropbox famously tested demand with a simple explainer video before building its full file-syncing product, growing its waitlist from a few thousand to tens of thousands of signups overnight. Zappos founder Nick Swinmurn validated online shoe sales by photographing shoes from local stores and manually fulfilling orders himself before investing in inventory. Airbnb’s founders tested their concept by renting out air mattresses in their own apartment during a conference.

What an MVP is not

A common misunderstanding treats an MVP as simply a low-quality or incomplete product. In the Lean Startup framework, an MVP is instead a deliberately scoped experiment designed to test a specific hypothesis about customer behavior. It should be viable enough to generate meaningful learning, even if it lacks the polish or feature set of a mature product.

The MVP’s lasting influence

The MVP concept has become a standard part of startup and product management vocabulary well beyond its original technology-sector context, influencing how teams in corporate innovation labs, nonprofits, and government agencies approach testing new ideas before committing significant resources. Its core insight, that early and cheap feedback beats late and expensive certainty, continues to shape product development practice.

Criticism and limitations

Critics of the minimum viable product approach caution that it can be misapplied, with teams releasing genuinely poor-quality products and excusing the shortcomings as intentional MVP learning rather than correcting a flawed approach. Some product leaders also argue the concept works better for software, where updates are cheap and fast, than for physical products or regulated industries, where releasing an incomplete version carries higher cost, safety, or compliance risk.

MVP versus prototype and proof of concept

The MVP is often confused with related but distinct concepts. A prototype is typically an early, often non-functional model used internally to visualize an idea, while a proof of concept tests whether a specific technical approach is feasible at all. An MVP, by contrast, is a functional product released to real customers specifically to gather market feedback, making it a later and more customer-facing step than either a prototype or a proof of concept.

The feedback loop beyond build-measure-learn

Successful use of an MVP depends heavily on clearly defining, before release, exactly which hypothesis is being tested and what metric will count as validation or rejection of that hypothesis. Teams that skip this step risk collecting data without a clear standard for interpreting it, undermining the methodology’s central promise of fast, decisive learning rather than open-ended experimentation with no end point.

MVPs in regulated and hardware industries

Industries such as medical devices, aviation, and pharmaceuticals face regulatory and safety requirements that limit how minimal an early product can be before real customer testing, since releasing an unsafe or non-compliant version is not a viable option. Teams in these sectors often adapt the MVP concept by testing smaller, lower-risk components of a larger system, or by using simulations and controlled pilot programs rather than releasing a true minimum version directly to the public.

MVP and the broader lean startup movement

The minimum viable product sits within a larger lean startup philosophy that also includes concepts such as the pivot, in which a company changes strategic direction based on what it learns, and validated learning, Ries’s term for insight gained through real customer behavior rather than opinion or assumption. Together, these ideas pushed startup culture toward treating a new venture as a series of testable hypotheses rather than a fixed plan to be executed exactly as written. A startup that validates its idea through a successful MVP often strengthens its position when later approaching venture capital investors for funding.

Measuring MVP success

Teams typically define success metrics before launching an MVP, such as signup conversion rate, retention after a set number of days, or willingness to pay, rather than judging the experiment informally after the fact. Clear, pre-defined metrics make it possible to decide objectively whether the data supports persevering with the current approach, adjusting it, or pivoting to a different idea entirely, which is the central discipline the build-measure-learn loop is meant to instill.

FAQs

Who coined the term ‘minimum viable product’?

Consultant Frank Robinson is generally credited with coining the term around 2001, though Eric Ries later popularized it widely.

What is the build-measure-learn loop?

A core concept from The Lean Startup in which teams build a minimal version of a product, measure real customer response, and use that data to decide whether to continue or change direction.

Editorially reviewed by Specialty Digest Editorial TeamLast reviewed November 1, 2026Researched and drafted with AI assistanceReport an issue