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 Feynman Technique |  Knowledge Modeling Knowledge Mapping |  Delivery RAID Log |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | 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 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 | Low | Medium | Low | Medium |
Timedifferent | 20-60 min | 1-3 h | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 1 | 3-12 | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Async | Workshop | Async | Workshop |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Knowledge Map, Critical Knowledge Areas, Transfer Plan | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | LearningKnowledgeUnderstanding | KnowledgeMappingRisk | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |