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
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration for Sailboat Retrospective
Agile
Sailboat 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 a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitydifferent
LowMediumLow
Timedifferent
5-20 min1-3 h45-90 min
Participantsdifferent
2-83-124-12
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Understanding Check, Clarification Notes, Learning GapsKnowledge Map, Critical Knowledge Areas, Transfer PlanSailboat Board, Risks, Improvement Actions
Tagsno overlap
LearningUnderstandingCommunication
KnowledgeMappingRisk
RetrospectiveTeamImprovement
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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 Feynman Technique.
Knowledge Modeling
Feynman Technique
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective