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 Architecture Decision Record Fishbone Diagram ATAM (Architecture Tradeoff Analysis Method)

Criterion	Knowledge Modeling Knowledge Mapping	Architecture Architecture Decision Record	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.	An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.	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	15-45 min	30-60 min	Several meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent	3-12	1-3	2-8	Evaluation team, architects, and relevant stakeholders
Formatdifferent	Workshop	Async	Workshop	Workshop + async
Outputdifferent	Knowledge Map, Critical Knowledge Areas, Transfer Plan	ADR File, Decision Log, Rationale	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	ArchitectureRationaleDocumentationGovernance	Root causeQualityOperations	ArchitectureQualityRiskTradeoffsStakeholders

Add more methods