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 |  Delivery RAID Log |  Decision Making Assumption Surfacing |  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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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 | 30 min Setup, dann laufend | 45-90 min | 1-3 h |
Participantsdifferent | 1-8 | 1-3 maintaining, briefing for everyone | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | RAID Log, Status Report Source | Assumption List, Critical Assumptions, Learning Plan | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | RiskTrackingStakeholdersGovernance | AssumptionsRiskDecisionDiscovery | KnowledgeMappingRisk |