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
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 Communication Plan
Delivery
Communication Plan
Paper illustration for Teach-back.
Knowledge Modeling
Teach-back
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Purposedifferent
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.When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.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.
Complexitysame
LowLowLowLow
Timedifferent
45–75 min45-90 min5-20 min45-90 min
Participantsdifferent
Team members involved2-62-83-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsCommunication Plan, Channel Matrix, Message CadenceUnderstanding Check, Clarification Notes, Learning GapsExpectation Map, Alignment Notes, Agreements
Tagsno overlap
RetrospectiveLearningReflectionTeam
CommunicationStakeholdersDeliveryPlanning
LearningUnderstandingCommunication
AlignmentStakeholdersTeam
Add more methods