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

Criterion	Facilitation Expectation Mapping	Operations Fishbone Diagram	Operations Fault Tree Analysis	Architecture ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent	When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.	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 critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.	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	Low	Low	High	High
Timedifferent	45-90 min	30-60 min	2-6 h	Several meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent	3-12	2-8	3-8	Evaluation team, architects, and relevant stakeholders
Formatdifferent	Workshop	Workshop	Workshop + async	Workshop + async
Outputdifferent	Expectation Map, Alignment Notes, Agreements	Fishbone Diagram, Cause Categories, Investigation Backlog	Fault Tree, Critical Paths, Cause Hypotheses, Control Actions	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	AlignmentStakeholdersTeam	Root causeQualityOperations	RiskRoot causeSafety	ArchitectureQualityRiskTradeoffsStakeholders

Add more methods