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:Game Day ATAM (Architecture Tradeoff Analysis Method)Fishbone Diagram Root Cause Tree Analysis

Criterion	DevOps Game Day	Architecture ATAM (Architecture Tradeoff Analysis Method)	Operations Fishbone Diagram	Operations Root Cause Tree Analysis
Purposedifferent	In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.	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 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.	For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.
Complexitydifferent	High	High	Low	Medium
Timedifferent	Halber Tag	Several meetings plus preparation and analysis; total effort depends on scope	30-60 min	1-3 h
Participantsdifferent	5-20	Evaluation team, architects, and relevant stakeholders	2-8	2-8
Formatdifferent	Workshop	Workshop + async	Workshop	Workshop
Outputdifferent	Simulation Notes, Gaps List, Updated Runbooks	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations	Fishbone Diagram, Cause Categories, Investigation Backlog	Cause Tree, Evidence Notes, Countermeasures
Tagsno overlap	ResilienceOperationsIncident	ArchitectureQualityRiskTradeoffsStakeholders	Root causeQualityOperations	Root causeTreeIncidentQuality

Add more methods