View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Product Strategy Lean Canvas | ![]() Agile NoEstimates | ![]() Innovation Lean Startup | ![]() Product Discovery Pretotyping |
|---|---|---|---|---|
Purposedifferent | When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 45-90 min | laufend | Wochen bis Monate je Lernzyklus | Stunden bis wenige Tage |
Participantsdifferent | 1-6 | 2-12 | 2-8 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Lean Canvas, Core Assumptions, Experiment Backlog | Throughput Data, Flow Forecast, Slicing Rules | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision |
Tagsno overlap | StartupLeanAssumptionsBusiness model | EstimationForecastingFlow | LeanStartupValidationMVP | ValidationDemandMVP |



