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
Anonymous individual judgments pass through feedback loops to form a distribution.
Decision Making
Delphi Method
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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.When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together.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 contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
2-6 h1-4 Wochen15-60 min je Zyklus1-3 h
Participantsdifferent
2-86-30 Experten1-82-8
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsExpert Forecast, Consensus Range, Assumption NotesSituation Assessment, Decision Loop, Action UpdatesContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
ForecastingExpertsDecisionStrategy
DecisionChangeLearningStrategy
Domain-Driven DesignBoundariesStrategy
Add more methods