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 |  Team Design Spotify Model Mapping |  Decision Making OODA Loop |
|---|---|---|---|---|
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. | When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | Half day initial, dann laufend | 45-90 min | 90-180 min | 15-60 min je Zyklus |
Participantsdifferent | Ein Team plus Stakeholder | 3-12 | 5-15 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Team API Document | Force Field Map, Change Levers, Risk Notes | Spotify Model Map, Action List | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | TeamAlignmentCommunicationService | ChangeDecisionStrategy | TeamOrganizationAlignmentDiagnosis | DecisionChangeLearningStrategy |