View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Concept Mapping |  Decision Making Assumption Surfacing |  Architecture Architecture Decision Record |  Knowledge Modeling Knowledge Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. | 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 | Medium | Low | Low | Medium |
Timedifferent | 1-2 h | 45-90 min | 15-45 min | 1-3 h |
Participantsdifferent | 1-8 | 2-8 | 1-3 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Assumption List, Critical Assumptions, Learning Plan | ADR File, Decision Log, Rationale | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | AssumptionsRiskDecisionDiscovery | ArchitectureRationaleDocumentationGovernance | KnowledgeMappingRisk |