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 Discovery Pretotyping |  Agile NoEstimates |  Innovation Lean Startup |  Product Strategy Lean Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | laufend | Wochen bis Monate je Lernzyklus | 45-90 min |
Participantsdifferent | 1-4 | 2-12 | 2-8 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Throughput Data, Flow Forecast, Slicing Rules | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Lean Canvas, Core Assumptions, Experiment Backlog |
Tagsno overlap | ValidationDemandMVP | EstimationForecastingFlow | LeanStartupValidationMVP | StartupLeanAssumptionsBusiness model |