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 |  Knowledge Modeling Feynman Technique |  Agile Start Stop Continue |  Agile Sprint 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. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | Half day initial, dann laufend | 20-60 min | 30-60 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | Ein Team plus Stakeholder | 1 | 3-12 | Scrum Team |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Team API Document | Plain-language Explanation, Knowledge Gaps, Study Notes | Start Stop Continue Board, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | TeamAlignmentCommunicationService | LearningKnowledgeUnderstanding | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementLearning |