Both methods are sold with the same sentence — validate before you build — and both usually get chosen on temperament rather than on risk. A deadline makes a sprint feel decisive; enough startup reading makes a loop feel rigorous. Neither choice was made against the thing that could actually kill the project.
The load-bearing distinction is cadence and commitment. Eric Ries’s Build-Measure-Learn is a discipline with no end date: name the leap-of-faith assumption, build the smallest thing that could disprove it, measure a number chosen in advance, decide to pivot or persevere, repeat. Jake Knapp’s Design Sprint is a single event with a fixed agenda: Monday to Friday, one room, a prototype by Thursday evening, five customers on Friday, an answer before the weekend. One is a loop. The other is a box.
Both sit in our product skills library, and an agent asked to “help us validate this” will produce either while rarely asking which risk you are carrying. New to the format? What an AI agent skill is covers it; this piece is about the methods.
What does each one actually produce?
A Design Sprint produces a decision and a list of specific confusions. The prototype is disposable; the durable output is the write-up — what all five testers understood, where each of them hesitated, which direction survived contact. Even when the concept dies on Friday, that list is worth the week.
Lean Startup produces validated learning and a pivot-or-persevere call: a hypothesis with a threshold attached, an MVP that is frequently not software, and instrumented behaviour over time — cohorts, one actionable metric nominated before the experiment ran, and innovation accounting that shows progress while revenue is roughly zero.
The epistemic gap matters more than either artefact. A sprint gathers five people reacting to a facade, once, in a room where they know they are watched. The loop gathers behaviour: what people did unmoderated, across a cohort, over weeks. Reactions are excellent evidence about comprehension and terrible evidence about demand.
Lean Startup vs Design Sprint: the comparison table
| Design Sprint | Lean Startup | |
|---|---|---|
| Shape | One five-day event, hour-by-hour agenda | A loop with no end date |
| Costs | Seven or fewer people for a week, plus recruiting five customers | Whatever the experiment costs — often a page and a week of traffic |
| Answers | Will people understand this, choose it, get through it? | Will people keep doing it, pay for it, come back? |
| Evidence | Five moderated interviews against a facade prototype | Instrumented behaviour, cohorts, one actionable metric |
| Risk it attacks | Desirability at first glance, and usability | Sustained desirability, and viability |
| Typical failure | The question was not worth a week, or Friday gets dropped | No threshold was written, so every result reads as encouraging |
| Ends | Friday | It does not |
Neither column is the rigorous one. A sprint with a leading interview script produces confident nonsense faster than any method available to you; a loop with no stated threshold produces a permanent state of promising early signals.
When is a Design Sprint the cheaper way to get the answer?
Twenty-five person-days is a real cost, and small next to a quarter spent building the wrong screen. Four conditions make the trade obvious:
- The risk has a visible surface — comprehension, choice between options, getting through a flow. If a person could react to it on a screen, the machinery fits.
- Two or more plausible directions, and an argument that has stopped producing new information. Wednesday hands the tie-break to one named person on purpose — the part a debate cannot do for itself.
- Five of the right customers are reachable this month. Recruiting is the underestimated constraint, and the one you can start before Monday.
- Someone in the room can act on Friday’s answer. Output that gets re-litigated by a committee has saved nobody anything.
The underrated benefit is front-loading: Monday forces you to write down what you are trying to learn, specifically enough that Friday can contradict it.
When is a Design Sprint theatre?
When the real risk is demand rather than design.
Five people react to a facade in a session where they were recruited, scheduled and thanked. They are being asked for an opinion, not for money. A prototype cannot charge a card, fail to be renewed, be found by a stranger through a search box, or be quietly abandoned in week three. If your open question is whether anyone pays, returns after the novelty, or arrives through an affordable channel, Friday hands you five articulate, unrepresentative reactions and a deck with the word validated on it.
A facade prototype can be misunderstood. It cannot be bought, renewed or abandoned — which is exactly why it settles design questions and cannot settle demand.
Three other tells: the decision was already made and the week exists to manufacture consent; nobody owns what happens after Friday; or the sprint is the only discovery the team does all year. The guard is cheap — before Monday, write down the result that would stop the build. If no outcome would change what you do next, spend the week talking to customers instead.
Can you run a Design Sprint inside Build-Measure-Learn?
Yes, and this is the honest relationship between them. A sprint is one turn of the loop with a fixed agenda and an unusually rich Measure step. Ries’s loop is deliberately silent about how you decide what to build — build the smallest thing that could disprove the assumption, it says, but not which smallest thing. Monday through Wednesday fills that gap.
Three compositions work: use the sprint to choose which experiment is worth instrumenting; run the loop after a sprint, because Friday’s patterns are hypotheses about behaviour rather than measurements of it; or drop a sprint into a stalled loop, when three iterations have moved nothing and the problem is the concept rather than the increments.
Two do not. A sprint followed by nothing — a decision with no way of finding out whether it was right. And a loop with no design step, which produces thin ships that each fail for a reason nobody can name afterwards.
Use the lean-startup skill to turn our sprint findings into a build-measure-learn plan — name the leap-of-faith assumption the prototype did not test, the smallest experiment that could disprove it, the single actionable metric, and the pivot-or-persevere threshold, all written down before we ship anything
Lean StartupWhere do The Mom Test and Continuous Discovery fit?
All four get confused because all four say “talk to customers.” They govern different things.
The Mom Test governs question quality, and it is not a process at all — it is a filter applied to sentences. It belongs to Friday’s interview script exactly as much as to a problem interview before the loop starts. Neither method has any defence against a leading question; a badly written script just gets you to the wrong conclusion by Friday evening rather than next quarter.
Continuous Discovery governs cadence. A sprint is an event and Build-Measure-Learn has no schedule attached; Torres supplies the rhythm that stops the year after a successful sprint from being evidence-free.
So: The Mom Test is the instrument, Design Sprint and Lean Startup are two schedules for using it, and Continuous Discovery keeps a schedule from lapsing when the quarter gets busy.
So which one should you run?
Work down the list and stop at the first line that matches.
- Your interview notes are full of compliments. Neither, yet — both will convert a leading question into a confident wrong answer.
- Nobody outside the building has reacted to the concept, and a large build starts soon. Design Sprint.
- Three plausible directions and an argument that has stopped moving. Design Sprint, for the Decider more than the prototype.
- The question is whether people pay, retain, or come back. Lean Startup. No prototype answers it.
- You launched, the chart goes up, and nobody can say whether the business works. Lean Startup — cohorts and one actionable metric instead of a growing total.
- You need an answer like this most weeks. Continuous Discovery; a repeated sprint is an expensive habit.
- You cannot say what result would change your mind. Neither. Write the threshold down first.
Frequently asked questions
Are Lean Startup and Design Sprint compatible, or do you have to pick one?
Compatible, at different grain. The sprint is a five-day container for one design question; Build-Measure-Learn decides whether the business underneath it works. Run the sprint as one turn of the loop — use it to choose what to build, then instrument the thin version and watch real behaviour. What fails is treating the sprint as a substitute, because a Friday verdict from five people is not a measurement of demand.
Can a Design Sprint replace an MVP?
No, though both involve something fake that customers see. A facade prototype exists to be reacted to in a moderated session; an MVP exists to be used, unsupervised, by people who chose it. The prototype can show that four of five testers never found the pricing. Only the MVP shows that nobody renewed.
Is five customer interviews really enough?
For the narrow claim, largely yes: a handful of moderated sessions surfaces most of the comprehension and usability problems in an interface, and Friday finds patterns across five rather than producing a statistic. Generalising it to demand is the mistake — five recruited people tell you nothing reliable about conversion, willingness to pay or retention, and any percentage derived from them is decorative.
What if we cannot get five days of everyone’s calendar?
Shortened variants circulate widely, and compressing the sketching and decision days is survivable. What does not compress is Monday’s framing — a sprint aimed at the wrong target answers the wrong question faster — and Friday. If you can only secure two days, you have a workshop, and three well-asked customer conversations would teach you more.
What does an AI agent actually add to either method?
Preparation, arithmetic, and one discipline that is hard to impose on yourself: pre-registration. Ask for the sprint questions, the target map, the prototype brief and the interview script; ask for the hypothesis, the metric definition and the pattern write-up. Then make it state the threshold before the experiment runs and hold you to it after, because the commonest failure in both methods is a result reinterpreted as encouraging once it arrives.
Where to go next
If the answer is the week, Design Sprint carries the schedule and writes the materials. If it is the loop, Lean Startup carries the MVP types, innovation accounting and the pivot taxonomy. If the honest answer was “our evidence is bad,” start with The Mom Test; if it was “we only do this once a year,” Continuous Discovery.
Our library packages canonical engineering and business books as agent skills — free, MIT-licensed, one command:
npx skills add wondelai/skills --all --globalAnd if you would rather have the discovery loop and the agent that runs it built for your team, that is the work we do.