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 | ![]() Operations After-Action Review | ![]() Operations Kepner-Tregoe | ![]() Decision Making OODA Loop |
|---|---|---|---|---|
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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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 | High | Medium |
Timedifferent | 45-90 min | 20-45 min | 2-8 h | 15-60 min je Zyklus |
Participantsdifferent | 3-12 | 3-12 | 2-8 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Force Field Map, Change Levers, Risk Notes | Lessons learned, Action items, Event summary | Problem Analysis, Decision Analysis, Risk Plan | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | ChangeDecisionStrategy | LearningOperationsImprovement | Problem solvingRoot causeDecisionOperations | DecisionChangeLearningStrategy |



