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

Criterion	Knowledge Modeling Knowledge Mapping	UX Research Empathy Mapping	Operations Fishbone Diagram	Architecture ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent	Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.	When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.	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	Low	Low	High
Timedifferent	1-3 h	30–60 min	30-60 min	Several meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent	3-12	4-8	2-8	Evaluation team, architects, and relevant stakeholders
Formatdifferent	Workshop	Workshop	Workshop	Workshop + async
Outputdifferent	Knowledge Map, Critical Knowledge Areas, Transfer Plan	Empathy Map, Assumptions List, Research Gaps	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	KnowledgeMappingRisk	SynthesisQualitativeWorkshop	Root causeQualityOperations	ArchitectureQualityRiskTradeoffsStakeholders

Add more methods