Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:SAAM (Software Architecture Analysis Method)Test Card Assumption Mapping Assumption Surfacing

Criterion	Architecture SAAM (Software Architecture Analysis Method)	Product Discovery Test Card	Product Discovery Assumption Mapping	Decision Making Assumption Surfacing
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.	Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.
Complexitydifferent	High	Low	Medium	Low
Timedifferent	Preparation, scenario analysis, and findings review; effort depends on scope	20-35 min	45-60 min	45-90 min
Participantsdifferent	Architecture experts and stakeholders for scenarios and weighting	1-5	2-8	2-8
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	Assumption List, Critical Assumptions, Learning Plan
Tagsno overlap	ArchitectureChangeAnalysisComparisonQuality	ExperimentsValidationDiscoveryHypothesis	AssumptionsRiskExperimentsValidation	AssumptionsRiskDecisionDiscovery

Add more methods