View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Strategic, Tactical and Operational PlanningRequest for CommentsOODA LoopForce Field Analysis
| Criterion |  Business Strategy Strategic, Tactical and Operational Planning |  Architecture Request for Comments |  Decision Making OODA Loop |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 90-180 min | 1-3 Wochen vom Draft bis zur Entscheidung | 15-60 min je Zyklus | 45-90 min |
Participantsdifferent | 4-12 | 3-20 Reviewer | 1-8 | 3-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Planning Levels Map, Cadence Model, Planning Artifact Inventory | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Situation Assessment, Decision Loop, Action Updates | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | CadenceGovernanceExecution | ArchitectureDecisionAsyncGovernance | DecisionChangeLearningStrategy | ChangeDecisionStrategy |