View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Force Field Analysis | ![]() Agile Start Stop Continue | ![]() Decision Making OODA Loop | ![]() Agile Sprint Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 30-60 min | 15-60 min je Zyklus | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 3-12 | 3-12 | 1-8 | Scrum Team |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Start Stop Continue Board, Improvement Actions | Situation Assessment, Decision Loop, Action Updates | Improvement actions, Team agreements |
Tagsno overlap | ChangeDecisionStrategy | RetrospectiveImprovementTeamReflection | DecisionChangeLearningStrategy | RetrospectiveImprovementLearning |



