View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Decision Making Argument Mapping |  Knowledge Modeling Concept Mapping |  Decision Making Red Teaming |
|---|---|---|---|---|
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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. |
Complexitydifferent | High | Medium | Medium | High |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h | 1-2 h | 1-4 h |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-8 | 1-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | 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 | Argument Map, Evidence Gaps, Decision Rationale | Concept Map, Relationship Labels, Knowledge Gaps | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | SensemakingDecisionRationale | KnowledgeConceptsMappingSensemaking | RiskDecisionSensemaking |