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 of DIBB with its method-specific working model.
Product Strategy
DIBB
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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.DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.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
MediumMediumLowMedium
Timedifferent
2-8 h15-60 min je Zyklus1-2 h1-3 h
Participantsdifferent
5-121-82-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsSituation Assessment, Decision Loop, Action UpdatesDIBB document, Belief list, Bet list, Learning reportContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
DecisionChangeLearningStrategy
StrategyDecisionAssumptionsHypothesis
Domain-Driven DesignBoundariesStrategy
Add more methods