View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Start Stop Continue |  Decision Making Force Field Analysis |  Agile Sprint Retrospective |  Decision Making OODA Loop |
|---|---|---|---|---|
Purposedifferent | 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 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 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. | 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 | Low | Medium |
Timedifferent | 30-60 min | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 15-60 min je Zyklus |
Participantsdifferent | 3-12 | 3-12 | Scrum Team | 1-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Force Field Map, Change Levers, Risk Notes | Improvement actions, Team agreements | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | RetrospectiveImprovementTeamReflection | ChangeDecisionStrategy | RetrospectiveImprovementLearning | DecisionChangeLearningStrategy |