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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
2-6 h30-90 min45-90 min1-2 h
Participantsdifferent
2-81-63-82-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsDecision Tree, Option Map, Assumption ListImpact Map, Outcome Hypotheses, Delivery OptionsDIBB document, Belief list, Bet list, Learning report
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
DecisionTreeOptions
OutcomesStrategyBehaviorPlanning
StrategyDecisionAssumptionsHypothesis
Add more methods