View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Quality Attribute Workshop |  Product Discovery Pretotyping |  Product Discovery Fake Door Test |
|---|---|---|---|
Purposedifferent | 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. | 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. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 2-4 h | Stunden bis wenige Tage | 1-5 Tage |
Participantsdifferent | 5-15 | 1-4 | Nutzertraffic |
Formatdifferent | Workshop | Workshop + async | Async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | RequirementsArchitectureWorkshop | ValidationDemandMVP | ValidationExperimentsDemandDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
