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 |  Architecture Quality Attribute Workshop |
|---|---|---|---|
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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | Stunden bis wenige Tage | 60-90 min | 2-4 h |
Participantsdifferent | 1-4 | 4-12 | 5-15 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Annotated Diagram, Prioritized Risk List, Action Backlog | Quality Scenarios, Priority List, Architecture Concerns |
Tagsno overlap | ValidationDemandMVP | RiskArchitectureWorkshopValidation | RequirementsArchitectureWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
