The Smallest Thing That Answers the Question
A minimum viable product is the least you can build to test the one assumption most likely to sink the idea. · 11 min
You do not have to build the whole idea to find out whether it will work. Building the whole thing first is the most expensive way to be wrong. Every new idea rests on a few things you are quietly hoping are true, and one of those hopes, if it turns out false, ends the idea no matter what else you get right. The job of a first build is not to impress anyone. It is to find out, as cheaply and quickly as it can, whether that one fragile hope holds.
Guess before you learn
You have an idea for an app that plans a week of meals and orders the groceries. What is the smallest first build that would best tell you whether people actually want it?
The riskiest thing in doubt is not whether an app can be built, but whether people will actually cook from a plan someone else makes. The handmade week tests exactly that, for almost nothing. If you guessed the landing page, keep the pencil mark: a signup measures curiosity, which is a weaker signal than someone using the plan. If you guessed 'wait,' notice that waiting spends the most expensive thing of all — time — and still teaches you nothing.
9–12
3–5
Every idea leans on a few things you hope are true. One of them matters most: if it is wrong, the whole idea falls over, no matter what else works. A minimum viable product is the smallest thing you can make to find out whether that one hope is real — before you spend months building the rest.
6–8
An assumption is something your idea needs to be true but you have not yet confirmed. Most ideas carry several. The one to test first is the riskiest assumption: the one you are least sure about and that would end the idea if it failed. A minimum viable product is the least you can build to test exactly that assumption — nothing more.
It can be rough. It can even be you doing the work by hand. What makes it viable is not polish but that it produces a real answer from real people.
9–12
Write your idea as a set of claims that all must hold for it to work: people have this problem, they will change what they do, they will pay, and you can reach them. Some of these you already know; others are only guesses. The guess whose failure would be fatal is the leap-of-faith assumption. A minimum viable product is the cheapest experiment that puts exactly that assumption to a real test — and returns evidence you can act on, not opinions.
K–2
You think friends will trade snacks for your drawings. Before you draw a hundred, draw one. Give it to one friend. Watch what they do. That single drawing tells you the biggest thing you need to know.
If your friend keeps it and asks for more, that is a yes. If they set it down and walk away, that is a no. One drawing told you, and you saved ninety-nine.
Undergrad
The term comes from Eric Ries's The Lean Startup: a minimum viable product is the version of a new offering that lets you collect the most validated learning about customers for the least effort. Its purpose is not revenue or reputation but learning — resolving the assumption most likely to be false before further resources are committed.
This reframes building. The question shifts from what should we make to what do we most need to learn, and what is the smallest thing that would teach it. Any feature not serving the current riskiest question is deferred, because it spends effort without reducing the risk that matters now.
Postgrad
Treat the decision as valuing information under uncertainty. Each candidate build carries a cost, a delay, and an expected reduction in your uncertainty about a specific assumption. The minimum viable product maximizes expected information per unit cost, concentrated on the assumption with the highest probability-weighted downside — the one whose failure destroys the most value.
Two forces set its size. Testing too little yields a signal too noisy to act on; testing too much pays for information you did not need yet and delays the moment of learning. The optimum is the smallest instrument that still lifts the fatal assumption clear of the noise.
minimum viable product
The least you can build to get an honest answer about the one assumption most likely to sink the idea. Often rough; sometimes no software at all.
So the first question is not what to build. It is which assumption to aim at. The right one carries two marks: you are guessing at it rather than knowing it, and the idea cannot survive if it is false. An assumption that is safe, or that you could be wrong about without much harm, can wait. Find the one that is both uncertain and fatal, and aim your smallest possible build at it.
Why is this true?
Why test the assumption most likely to be wrong, instead of the one that is easiest to build?
Because the cheapest thing you can buy is the knowledge that the idea is doomed, before you spend a year on it. Building the easy part first feels productive, but it leaves the fatal question unanswered — and answers it last, when it is most expensive to hear.
To find that assumption, write the idea as a short list of things that must be true for it to work. Then, beside each one, mark whether you actually know it or are only hoping. The riskiest is the hope whose failure would sink everything, and that is where the first build points. The build itself should be the least you can make that still forces a real answer — often no software at all, just you doing the work by hand for a handful of real people.
Choose the cheapest minimum viable product for a meal-planning service — the steps fade as you master them
People will actually cook from a plan that someone else makes.
Hand-make one week of meal plans for five volunteers — no app.
At least three of the five cook four or more of the planned meals.
A minimum viable product is not a small version of the finished thing. It is a test, built just solidly enough to get an honest answer. Next, you will meet the cheapest build of all: doing the whole job by hand, for real customers, before a single line of the product exists.
Note
Stuck naming the riskiest assumption? The Atelier of Mind — practice for how you think — has a short drill on separating what you know from what you only hope.
Practice — new ink and old, interleaved
1.Rewrite 'Would this app be helpful to you?' as a discovery question. Which is best?
2.In a discovery interview, why do you ask what the person did the last time the problem came up, rather than what they would do in future?
3.You can reach 1,200 people, 15% of whom would buy, each spending $80 a year. What yearly market can you reach, in dollars?
4.At $240 per customer per year, what is the yearly revenue from 300 reachable customers, in dollars?
5.Which is the strongest sign that a problem is worth building on?
6.Which of these is a proper value proposition?
7.Why is a problem that happens daily usually worth more than one that happens once a year?
8.You want to test whether people will use a plant-watering reminder service. Which is the best minimum viable product?
9.You can reach about 400 dog owners in your town, and roughly 1 in 4 would plausibly pay for weekly walks. About how many paying customers is that, at most?