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 |  Team Design Team Topologies Interaction Modes |  Team Design Spotify Model 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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | 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 | Medium | Medium | Low |
Timedifferent | 5-20 min | Half day | 90-180 min | 45–75 min |
Participantsdifferent | 2-8 | Team-Leads plus Architecture | 5-15 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | LearningUnderstandingCommunication | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis | RetrospectiveLearningReflectionTeam |