View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Runbook |  Product Discovery Assumption Mapping |  Decision Making OODA Loop |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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. | 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 | Low | Medium | Medium | Low |
Timedifferent | 20-60 min | 45-60 min | 15-60 min je Zyklus | 45-90 min |
Participantsdifferent | 1-4 | 2-8 | 1-8 | 3-12 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Runbook, Checklist, Escalation Path | Assumption map, Test backlog, Risk ranking | Situation Assessment, Decision Loop, Action Updates | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | OperationsReliabilityDocumentation | AssumptionsRiskExperimentsValidation | DecisionChangeLearningStrategy | ChangeDecisionStrategy |