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 Lotus Blossom |
|---|---|---|---|
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. | When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. |
Complexitysame | Low | Low | Low |
Timedifferent | Stunden bis wenige Tage | 60-90 min | 45-90 min |
Participantsdifferent | 1-4 | 4-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Annotated Diagram, Prioritized Risk List, Action Backlog | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | ValidationDemandMVP | RiskArchitectureWorkshopValidation | BrainstormingIdeationCreativityDivergenceWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
