methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Teach-back.
Knowledge Modeling
Teach-back
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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 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.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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitydifferent
LowLowMediumLow
Timedifferent
5-20 min45–75 min1-3 h30-60 min
Participantsdifferent
2-8Team members involved3-123-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Understanding Check, Clarification Notes, Learning Gaps4Ls Board, Learning Themes, Improvement ActionsKnowledge Map, Critical Knowledge Areas, Transfer PlanStart Stop Continue Board, Improvement Actions
Tagsno overlap
LearningUnderstandingCommunication
RetrospectiveLearningReflectionTeam
KnowledgeMappingRisk
RetrospectiveImprovementTeamReflection
Add more methods