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 MappingConcept MappingExpectation MappingATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Knowledge Modeling Knowledge Mapping |  Knowledge Modeling Concept Mapping |  Facilitation Expectation Mapping |  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. | 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. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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 | Medium | Low | High |
Timedifferent | 1-3 h | 1-2 h | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-12 | 1-8 | 3-12 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Concept Map, Relationship Labels, Knowledge Gaps | Expectation Map, Alignment Notes, Agreements | 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 | KnowledgeConceptsMappingSensemaking | AlignmentStakeholdersTeam | ArchitectureQualityRiskTradeoffsStakeholders |