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 SAAM (Software Architecture Analysis Method) |  Product Discovery MVP Test Matrix |  Product Discovery Fake Door Test |  Product Discovery Smoke Test |
|---|---|---|---|---|
Purposedifferent | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | When several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan. | 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. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 45-75 min | 1-5 Tage | 1-5 Tage |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-8 | Nutzertraffic | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Test Matrix, Test Plan | Click Data, Interest Signal, Learning Decision | Interest Metrics, Conversion Signal, Learning Note |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | ExperimentsValidationDiscoveryOptions | ValidationExperimentsDemandDiscovery | ValidationExperimentsDemandGrowth |