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 |  Agile Sailboat Retrospective |  Knowledge Modeling Feynman Technique |  Agile Starfish Retrospective |
|---|---|---|---|---|
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. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 5-20 min | 45-90 min | 20-60 min | 45-90 min |
Participantsdifferent | 2-8 | 4-12 | 1 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Sailboat Board, Risks, Improvement Actions | Plain-language Explanation, Knowledge Gaps, Study Notes | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | LearningUnderstandingCommunication | RetrospectiveTeamImprovement | LearningKnowledgeUnderstanding | RetrospectiveImprovementExperimentsTeam |