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 Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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 a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.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.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
1-3 h1-3 h15-60 min je Zyklus45-90 min
Participantsdifferent
3-123-101-83-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
System Map, Dependencies, Leverage PointsDomain Context Map, Boundary Notes, Ownership MapSituation Assessment, Decision Loop, Action UpdatesForce Field Map, Change Levers, Risk Notes
Tagsno overlap
Systems thinkingMappingBoundariesChange
Domain-Driven DesignContextBoundaries
DecisionChangeLearningStrategy
ChangeDecisionStrategy
Add more methods