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 |  Knowledge Modeling Concept Mapping |  Delivery RAID Log |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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. | 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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-2 h | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 3-12 | 1-8 | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Concept Map, Relationship Labels, Knowledge Gaps | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | KnowledgeMappingRisk | KnowledgeConceptsMappingSensemaking | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |