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 Test Card |  Product Discovery Assumption Mapping |  Product Discovery Experiment Canvas |
|---|---|---|---|---|
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. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 20-35 min | 45-60 min | 30-60 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 1-5 | 2-8 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + 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 Card with a pre-set threshold | Assumption map, Test backlog, Risk ranking | Completed Experiment Canvas, Success Metric |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | ExperimentsValidationDiscoveryHypothesis | AssumptionsRiskExperimentsValidation | ExperimentsValidationDiscoveryHypothesis |