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 Teach-back | ![]() Delivery RAID Log | ![]() Knowledge Modeling Feynman Technique | ![]() Knowledge Modeling Knowledge Mapping |
|---|---|---|---|---|
Purposedifferent | Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations. | 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 5-20 min | 30 min Setup, dann laufend | 20-60 min | 1-3 h |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 1 | 3-12 |
Formatdifferent | Workshop + async | Async | Async | Workshop |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | RAID Log, Status Report Source | Plain-language Explanation, Knowledge Gaps, Study Notes | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | LearningUnderstandingCommunication | RiskTrackingStakeholdersGovernance | LearningKnowledgeUnderstanding | KnowledgeMappingRisk |



