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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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.Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.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
MediumMediumMediumMedium
Timedifferent
30-90 min1-3 h1-3 h15-60 min je Zyklus
Participantsdifferent
1-62-83-121-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Decision Tree, Option Map, Assumption ListContext Map, Integration Patterns, Boundary NotesSystem Map, Dependencies, Leverage PointsSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
DecisionTreeOptions
Domain-Driven DesignBoundariesStrategy
Systems thinkingMappingBoundariesChange
DecisionChangeLearningStrategy
Add more methods