methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Purposedifferent
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 many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.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
MediumMediumMediumLow
Timedifferent
15-60 min je Zyklus30-90 min1-3 h45-90 min
Participantsdifferent
1-83-122-83-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Situation Assessment, Decision Loop, Action UpdatesAffinity Size Map, Grouped Estimates, Unclear ItemsContext Map, Integration Patterns, Boundary NotesForce Field Map, Change Levers, Risk Notes
Tagsno overlap
DecisionChangeLearningStrategy
EstimationBacklogRelative sizing
Domain-Driven DesignBoundariesStrategy
ChangeDecisionStrategy
Add more methods