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 |  Business Strategy McKinsey 7S |  Decision Making Force Field Analysis |  Decision Making OODA Loop |
|---|---|---|---|---|
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. | McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result. | 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. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 60-90 min pro Feature | 2-4 h | 45-90 min | 15-60 min je Zyklus |
Participantsdifferent | 3-6 | 3-12 | 3-12 | 1-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | 7S Assessment, Alignment Gaps, Change Actions | Force Field Map, Change Levers, Risk Notes | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | OrganizationStrategyAlignmentChange | ChangeDecisionStrategy | DecisionChangeLearningStrategy |