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:Failure Scenario Analysis Smoke Test ATAM (Architecture Tradeoff Analysis Method)Assumption Mapping

Criterion	Engineering Failure Scenario Analysis	Product Discovery Smoke Test	Architecture ATAM (Architecture Tradeoff Analysis Method)	Product Discovery Assumption Mapping
Purposedifferent	In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage.	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.	ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.	When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent	Medium	Low	High	Medium
Timedifferent	1-3 h	1-5 Tage	Several meetings plus preparation and analysis; total effort depends on scope	45-60 min
Participantsdifferent	3-8	Nutzertraffic	Evaluation team, architects, and relevant stakeholders	2-8
Formatdifferent	Workshop	Async	Workshop + async	Workshop + async
Outputdifferent	Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions	Interest Metrics, Conversion Signal, Learning Note	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations	Assumption map, Test backlog, Risk ranking
Tagsno overlap	FailureResilienceRisk	ValidationExperimentsDemandGrowth	ArchitectureQualityRiskTradeoffsStakeholders	AssumptionsRiskExperimentsValidation

Add more methods