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 Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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.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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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.
Complexitysame
LowLowLowLow
Timedifferent
5-20 min45-90 min30-60 min45-90 min
Participantsdifferent
2-83-123-124-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Understanding Check, Clarification Notes, Learning GapsExpectation Map, Alignment Notes, AgreementsStart Stop Continue Board, Improvement ActionsSailboat Board, Risks, Improvement Actions
Tagsno overlap
LearningUnderstandingCommunication
AlignmentStakeholdersTeam
RetrospectiveImprovementTeamReflection
RetrospectiveTeamImprovement
Add more methods