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 Accountability Ladder
Operations
Accountability Ladder
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
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
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.With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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
LowLowLowLow
Timedifferent
5-20 min20-45 min45-90 min45–75 min
Participantsdifferent
2-81-83-12Team members involved
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Understanding Check, Clarification Notes, Learning GapsOwnership Reflection, Action Commitment, Coaching NotesExpectation Map, Alignment Notes, Agreements4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
LearningUnderstandingCommunication
ResponsibilityLeadershipTeam
AlignmentStakeholdersTeam
RetrospectiveLearningReflectionTeam
Add more methods