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
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Paper illustration for Intervention Mapping.
Systems Thinking
Intervention Mapping
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain.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.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
MediumHighLowMedium
Timedifferent
2-8 h1-5 Tage45-90 min15-60 min je Zyklus
Participantsdifferent
5-124-123-121-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsLogic Model, Change Objectives, Intervention Components, Evaluation PlanForce Field Map, Change Levers, Risk NotesSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
ChangeSystems thinkingCapability
ChangeDecisionStrategy
DecisionChangeLearningStrategy
Add more methods