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:Impact Mapping ATAM (Architecture Tradeoff Analysis Method)Fishbone Diagram Alignment Mapping

Criterion	Product Strategy Impact Mapping	Architecture ATAM (Architecture Tradeoff Analysis Method)	Operations Fishbone Diagram	Facilitation Alignment Mapping
Purposedifferent	When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.	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.	When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent	Medium	High	Low	Medium
Timedifferent	45-90 min	Several meetings plus preparation and analysis; total effort depends on scope	30-60 min	1-2 h
Participantsdifferent	3-8	Evaluation team, architects, and relevant stakeholders	2-8	4-12
Formatdifferent	Workshop	Workshop + async	Workshop	Workshop
Outputdifferent	Impact Map, Outcome Hypotheses, Delivery Options	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	Alignment Map, Open Issues, Decision Questions
Tagsno overlap	OutcomesStrategyBehaviorPlanning	ArchitectureQualityRiskTradeoffsStakeholders	Root causeQualityOperations	AlignmentStakeholdersStrategyFacilitation

Add more methods