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 Specification by Example |  Decision Making OODA Loop |  Decision Making Assumption Surfacing |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 | Low | Low |
Timedifferent | 60-90 min pro Feature | 15-60 min je Zyklus | 45-90 min | 45-90 min |
Participantsdifferent | 3-6 | 1-8 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Situation Assessment, Decision Loop, Action Updates | Assumption List, Critical Assumptions, Learning Plan | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | DecisionChangeLearningStrategy | AssumptionsRiskDecisionDiscovery | ChangeDecisionStrategy |