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 |  Knowledge Modeling Knowledge Mapping |  Facilitation Responsibility Poker |  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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 5-20 min | 1-3 h | 45-90 min | 45–75 min |
Participantsdifferent | 2-8 | 3-12 | 3-10 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Responsibility Map, Role Agreements, Open Questions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | LearningUnderstandingCommunication | KnowledgeMappingRisk | RolesResponsibilityTeamFacilitation | RetrospectiveLearningReflectionTeam |