Guides · Minimum viable product

What is a minimum viable product

10 November 2026 · Escherbridge

In GAO's Agile Assessment Guide, a minimum viable product is "a version of a working product that allows the team to learn from and interact with their customer with the least amount of effort" — and it "should not simply represent the smallest piece of functionality." If no one can use a working product and give feedback, it is not yet an MVP in the sense GAO bothers to define.

This is a field definition, not a growth-hacking post. It is not a rewrite of the live essay A page that looks like a business is not a business; that essay is the sibling. The document is the same September 2020 Exposure Draft of the GAO Agile Assessment Guide used in the working-software guide. It is not called a later final edition. Eric Ries's 2011 book The Lean Startup is named only as GAO names it, as the book that popularized the concept. Additional lines from that book were not opened and are not invented here.

The GAO Agile Assessment Guide says "The minimum viable product (MVP) is a valuable tool to elicit feedback by demonstrating aspects to the developing solution."

The guide's definitional box: "A concept popularized in Eric Ries' 2011 book, The Lean Startup, the MVP is a version of a working product that allows the team to learn from and interact with their customer with the least amount of effort." "An MVP allows the team to better understand their customers' needs and interests without committing a large number of resources or developing a completed product."

The limit, still in GAO's words: "If done correctly, the MVP can allow a team to refine the product early in development to ensure it meets customer' needs rather than later in development when updates might be expensive or cost-prohibitive. This could mean significant updates to the product or even abandonment of the product altogether, but ensures the team is working on a product that the customer actually wants." "However, teams must remember that an MVP is only valuable if the product is sufficiently developed to allow for customer interaction and to elicit feedback and learning. The MVP should not simply represent the smallest piece of functionality."

What this does and does not say

Working product; learn and interact; least amount of effort; not a completed product; valuable only if sufficiently developed to elicit feedback; not merely the smallest piece of functionality. Abandonment is allowed when that is what the learning says. A landing page, a waitlist, or a pitch deck is not, on this definition, an MVP. This page does not invent success rates for "doing MVP correctly," and it does not invent a house MVP, a client, or a conversion rate.

The first conversation still ends with a yes, a no, or a better idea, at Start.

The useful next step is to ask whether a working product can already be used and learned from. If something on this page is wrong, write to us.

Author: Escherbridge. Last reviewed: 2026-11-10, America/Denver.