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 Smoke Test |  Product Discovery Assumption Mapping |  Product Discovery Fake Door 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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 | High | Low | Medium | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 1-5 Tage | 45-60 min | 1-5 Tage |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | Nutzertraffic | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | 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 | Interest Metrics, Conversion Signal, Learning Note | Assumption map, Test backlog, Risk ranking | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | ValidationExperimentsDemandGrowth | AssumptionsRiskExperimentsValidation | ValidationExperimentsDemandDiscovery |