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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Purposedifferent
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.A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation.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.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.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
1-3 h2-4 h15-60 min je Zyklus1-3 h
Participantsdifferent
2-83-81-83-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Context Map, Integration Patterns, Boundary NotesFuture Reality Tree, Negative Branches, Assumption List, Improved InjectionsSituation Assessment, Decision Loop, Action UpdatesSystem Map, Dependencies, Leverage Points
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
Theory of ConstraintsSystems thinkingChange
DecisionChangeLearningStrategy
Systems thinkingMappingBoundariesChange
Add more methods