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 |  Knowledge Modeling Teach-back |  Facilitation Stakeholder Mapping |
|---|---|---|---|
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. | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitysame | Low | Low | Low |
Timedifferent | 45–75 min | 5-20 min | 60–90 min |
Participantsdifferent | Team members involved | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Understanding Check, Clarification Notes, Learning Gaps | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | RetrospectiveLearningReflectionTeam | LearningUnderstandingCommunication | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
