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 Change Analysis |  Domain Modeling Domain Context Map |  Decision Making OODA Loop |
|---|---|---|---|
Purposedifferent | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 45-120 min | 1-3 h | 15-60 min je Zyklus |
Participantsdifferent | 2-6 | 3-10 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Domain Context Map, Boundary Notes, Ownership Map | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | Domain-Driven DesignContextBoundaries | DecisionChangeLearningStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
