View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Knowledge Modeling Teach-back |  Architecture Architecture Communication Canvas |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 5-20 min | 60-120 min | 45–75 min |
Participantsdifferent | 3-12 | 2-8 | 2-8 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Understanding Check, Clarification Notes, Learning Gaps | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | AlignmentStakeholdersTeam | LearningUnderstandingCommunication | ArchitectureCommunicationStakeholdersCanvas | RetrospectiveLearningReflectionTeam |