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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Intervention Mapping.
Systems Thinking
Intervention Mapping
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Purposedifferent
Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.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 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
MediumHighMediumLow
Timedifferent
2-6 h1-5 Tage15-60 min je Zyklus45-90 min
Participantsdifferent
2-84-121-83-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsLogic Model, Change Objectives, Intervention Components, Evaluation PlanSituation Assessment, Decision Loop, Action UpdatesForce Field Map, Change Levers, Risk Notes
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
ChangeSystems thinkingCapability
DecisionChangeLearningStrategy
ChangeDecisionStrategy
Add more methods