View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Agile 4Ls Retrospective |  Knowledge Modeling Teach-back |  Knowledge Modeling Feynman Technique |
|---|---|---|---|---|
Purposedifferent | 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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | Half day initial, dann laufend | 45–75 min | 5-20 min | 20-60 min |
Participantsdifferent | Ein Team plus Stakeholder | Team members involved | 2-8 | 1 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Team API Document | 4Ls Board, Learning Themes, Improvement Actions | Understanding Check, Clarification Notes, Learning Gaps | Plain-language Explanation, Knowledge Gaps, Study Notes |
Tagsno overlap | TeamAlignmentCommunicationService | RetrospectiveLearningReflectionTeam | LearningUnderstandingCommunication | LearningKnowledgeUnderstanding |