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
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
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
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.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
45-90 min1-3 h1-3 h15-60 min je Zyklus
Participantsdifferent
3-122-83-121-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Force Field Map, Change Levers, Risk NotesContext Map, Integration Patterns, Boundary NotesSystem Map, Dependencies, Leverage PointsSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
ChangeDecisionStrategy
Domain-Driven DesignBoundariesStrategy
Systems thinkingMappingBoundariesChange
DecisionChangeLearningStrategy
Add more methods