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 Example Mapping |  Decision Making OODA Loop |  Agile Specification by Example |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. | 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 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 | 30-60 min | 15-60 min je Zyklus | 60-90 min pro Feature | 45-90 min |
Participantsdifferent | 3-7 | 1-8 | 3-6 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Situation Assessment, Decision Loop, Action Updates | Example Table, Acceptance Tests | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | DecisionChangeLearningStrategy | AgileRequirementsExamplesBehavior-Driven Development | ChangeDecisionStrategy |