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 |  Agile 4Ls Retrospective |  Operations Learning Review |
|---|---|---|---|
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 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | Half day initial, dann laufend | 45–75 min | 1-3 h |
Participantsdifferent | Ein Team plus Stakeholder | Team members involved | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Team API Document | 4Ls Board, Learning Themes, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | TeamAlignmentCommunicationService | RetrospectiveLearningReflectionTeam | LearningRetrospectiveIncidentOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
