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 Knowledge Mapping |  Architecture Risk Storming |  Decision Making Assumption Surfacing |  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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. | 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 | Low | Medium |
Timedifferent | 1-3 h | 60-90 min | 45-90 min | 1-2 h |
Participantsdifferent | 3-12 | 4-12 | 2-8 | 1-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Annotated Diagram, Prioritized Risk List, Action Backlog | Assumption List, Critical Assumptions, Learning Plan | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | KnowledgeMappingRisk | RiskArchitectureWorkshopValidation | AssumptionsRiskDecisionDiscovery | KnowledgeConceptsMappingSensemaking |