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 MappingAfter-Action ReviewATAM (Architecture Tradeoff Analysis Method)Concept Mapping
| Criterion |  Knowledge Modeling Knowledge Mapping |  Operations After-Action Review |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. | 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. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 20-45 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h |
Participantsdifferent | 3-12 | 3-12 | Evaluation team, architects, and relevant stakeholders | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Lessons learned, Action items, Event summary | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | KnowledgeMappingRisk | LearningOperationsImprovement | ArchitectureQualityRiskTradeoffsStakeholders | KnowledgeConceptsMappingSensemaking |