View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Facilitation Team Charter |  Knowledge Modeling Teach-back |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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 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 | Low | Low |
Timedifferent | Half day initial, dann laufend | 2-4 h | 5-20 min | 45–75 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-12 | 2-8 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Team API Document | Team Charter, Working Norms, Role Notes | Understanding Check, Clarification Notes, Learning Gaps | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | TeamAlignmentCommunicationService | TeamAlignmentCollaboration | LearningUnderstandingCommunication | RetrospectiveLearningReflectionTeam |