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) |  Architecture Risk Storming |  Product Discovery Smoke Test |  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. | 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. | 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 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 | Low | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 60-90 min | 1-5 Tage | 1-5 Tage |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 4-12 | 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 | Annotated Diagram, Prioritized Risk List, Action Backlog | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | RiskArchitectureWorkshopValidation | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery |