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 |  Knowledge Modeling Feynman Technique |  Team Design Team API |  Facilitation Team Charter |
|---|---|---|---|---|
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. | 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. | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 5-20 min | 20-60 min | Half day initial, dann laufend | 2-4 h |
Participantsdifferent | 2-8 | 1 | Ein Team plus Stakeholder | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Plain-language Explanation, Knowledge Gaps, Study Notes | Team API Document | Team Charter, Working Norms, Role Notes |
Tagsno overlap | LearningUnderstandingCommunication | LearningKnowledgeUnderstanding | TeamAlignmentCommunicationService | TeamAlignmentCollaboration |