View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile 4Ls Retrospective |  Team Design Team API |  Knowledge Modeling Feynman Technique |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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 |
Timedifferent | 45–75 min | Half day initial, dann laufend | 20-60 min |
Participantsdifferent | Team members involved | Ein Team plus Stakeholder | 1 |
Formatdifferent | Workshop | Workshop + async | Async |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Team API Document | Plain-language Explanation, Knowledge Gaps, Study Notes |
Tagsno overlap | RetrospectiveLearningReflectionTeam | TeamAlignmentCommunicationService | LearningKnowledgeUnderstanding |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
