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 OODA Loop.
Decision Making
OODA Loop
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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.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.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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
2-8 h15-60 min je Zyklus1-2 h45-90 min
Participantsdifferent
5-121-84-123-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsSituation Assessment, Decision Loop, Action UpdatesAlignment Map, Open Issues, Decision QuestionsForce Field Map, Change Levers, Risk Notes
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
DecisionChangeLearningStrategy
AlignmentStakeholdersStrategyFacilitation
ChangeDecisionStrategy
Add more methods