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 |  Delivery RAID Log |  Innovation Lean Startup |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | 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. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 30 min Setup, dann laufend | Wochen bis Monate je Lernzyklus | 45-60 min |
Participantsdifferent | 1-4 | 1-3 maintaining, briefing for everyone | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | RAID Log, Status Report Source | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ValidationDemandMVP | RiskTrackingStakeholdersGovernance | LeanStartupValidationMVP | AssumptionsRiskExperimentsValidation |