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 Starfish Retrospective |  Agile 4Ls 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 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. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 5-20 min | 45-90 min | 45–75 min |
Participantsdifferent | 2-8 | 4-12 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | LearningUnderstandingCommunication | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
