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:Design Studio Fault Tree Analysis Fishbone Diagram ATAM (Architecture Tradeoff Analysis Method)

Criterion	UX Design Design Studio	Operations Fault Tree Analysis	Operations Fishbone Diagram	Architecture ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent	When several designs need to be quickly put in relation to each other, it makes ideas visible and comparable. It encourages early variants instead of long upfront debates.	For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.	When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.	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.
Complexitydifferent	Medium	High	Low	High
Timedifferent	1-3 h	2-6 h	30-60 min	Several meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent	3-8	3-8	2-8	Evaluation team, architects, and relevant stakeholders
Formatdifferent	Workshop	Workshop + async	Workshop	Workshop + async
Outputdifferent	Sketches, Concept Directions, Design Decisions	Fault Tree, Critical Paths, Cause Hypotheses, Control Actions	Fishbone Diagram, Cause Categories, Investigation Backlog	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap	SketchingCollaborationIdeation	RiskRoot causeSafety	Root causeQualityOperations	ArchitectureQualityRiskTradeoffsStakeholders

Add more methods