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:ATAM (Architecture Tradeoff Analysis Method)Standard Work Analysis Concept Mapping Knowledge Mapping

Criterion	Architecture ATAM (Architecture Tradeoff Analysis Method)	Operations Standard Work Analysis	Knowledge Modeling Concept Mapping	Knowledge Modeling Knowledge Mapping
Purposedifferent	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 the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude.	Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.	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.
Complexitydifferent	High	Medium	Medium	Medium
Timedifferent	Several meetings plus preparation and analysis; total effort depends on scope	1-3 h	1-2 h	1-3 h
Participantsdifferent	Evaluation team, architects, and relevant stakeholders	2-6	1-8	3-12
Formatdifferent	Workshop + async	Workshop	Workshop + async	Workshop
Outputdifferent	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations	Standard Work Sheet, Deviation List, Improved Standard, Training Needs	Concept Map, Relationship Labels, Knowledge Gaps	Knowledge Map, Critical Knowledge Areas, Transfer Plan
Tagsno overlap	ArchitectureQualityRiskTradeoffsStakeholders	LeanProcessQuality	KnowledgeConceptsMappingSensemaking	KnowledgeMappingRisk

Add more methods