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
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
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.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.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 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
MediumLowMediumMedium
Timedifferent
1-3 h30-90 min1-3 h15-60 min je Zyklus
Participantsdifferent
3-122-82-81-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
System Map, Dependencies, Leverage PointsConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesContext Map, Integration Patterns, Boundary NotesSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
Systems thinkingMappingBoundariesChange
ConstraintsDecisionPlanningOptions
Domain-Driven DesignBoundariesStrategy
DecisionChangeLearningStrategy
Add more methods