View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Lean Startup | ![]() Delivery RAID Log | ![]() Product Discovery Pretotyping | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | Wochen bis Monate je Lernzyklus | 30 min Setup, dann laufend | Stunden bis wenige Tage | 45-60 min |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 1-4 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | RAID Log, Status Report Source | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | LeanStartupValidationMVP | RiskTrackingStakeholdersGovernance | ValidationDemandMVP | AssumptionsRiskExperimentsValidation |



