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 Spotify Model Mapping |  Decision Making OODA Loop |  Facilitation Expectation Mapping |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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 | Medium | Medium | Low | Low |
Timedifferent | 90-180 min | 15-60 min je Zyklus | 45-90 min | 45-90 min |
Participantsdifferent | 5-15 | 1-8 | 3-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Situation Assessment, Decision Loop, Action Updates | Expectation Map, Alignment Notes, Agreements | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | DecisionChangeLearningStrategy | AlignmentStakeholdersTeam | ChangeDecisionStrategy |