View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Teach-back |  Delivery Communication Plan |  Facilitation Expectation Mapping |  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. | 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. | 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 | Low | Low | Low | Low |
Timedifferent | 5-20 min | 45-90 min | 45-90 min | 45–75 min |
Participantsdifferent | 2-8 | 2-6 | 3-12 | Team members involved |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Communication Plan, Channel Matrix, Message Cadence | Expectation Map, Alignment Notes, Agreements | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | LearningUnderstandingCommunication | CommunicationStakeholdersDeliveryPlanning | AlignmentStakeholdersTeam | RetrospectiveLearningReflectionTeam |