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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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.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.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.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 h30-90 min45-90 min1-3 h
Participantsdifferent
3-121-63-122-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
System Map, Dependencies, Leverage PointsDecision Tree, Option Map, Assumption ListForce Field Map, Change Levers, Risk NotesContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
Systems thinkingMappingBoundariesChange
DecisionTreeOptions
ChangeDecisionStrategy
Domain-Driven DesignBoundariesStrategy
Add more methods