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 Design Charrette |  Innovation Brainstorming |
|---|---|---|---|---|
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. | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | Stunden bis wenige Tage | 60-90 min | Halber Tag bis mehrere Tage | 30-60 min |
Participantsdifferent | 1-4 | 4-12 | 10-50 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Annotated Diagram, Prioritized Risk List, Action Backlog | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | ValidationDemandMVP | RiskArchitectureWorkshopValidation | BrainstormingWorkshopCollaborationIdeation | BrainstormingIdeationCreativityWorkshopDivergence |