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 |  Architecture Risk Storming |  Innovation Lean Startup |
|---|---|---|---|
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 architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | Stunden bis wenige Tage | 60-90 min | Wochen bis Monate je Lernzyklus |
Participantsdifferent | 1-4 | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Annotated Diagram, Prioritized Risk List, Action Backlog | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision |
Tags1 shared | ValidationDemandMVP | RiskArchitectureWorkshopValidation | LeanStartupValidationMVP |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
