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 |  Decision Making Force Field Analysis |  Decision Making OODA Loop |  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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | 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 | Half day initial, dann laufend | 45-90 min | 15-60 min je Zyklus | 45–75 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-12 | 1-8 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Team API Document | Force Field Map, Change Levers, Risk Notes | Situation Assessment, Decision Loop, Action Updates | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | TeamAlignmentCommunicationService | ChangeDecisionStrategy | DecisionChangeLearningStrategy | RetrospectiveLearningReflectionTeam |