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 OODA Loop |  Decision Making Force Field Analysis |
|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | Half day initial, dann laufend | 15-60 min je Zyklus | 45-90 min |
Participantsdifferent | Ein Team plus Stakeholder | 1-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Team API Document | Situation Assessment, Decision Loop, Action Updates | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | TeamAlignmentCommunicationService | DecisionChangeLearningStrategy | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
