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
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
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 size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets.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.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
LowMediumLowMedium
Timedifferent
5-20 min2-6 h1-2 h1-3 h
Participantsdifferent
3-202-82-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsEvent Model, UI Flow, Commands, Read ModelsDIBB document, Belief list, Bet list, Learning reportContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
EstimationEffortRisk
EventsBlueprintDomain-Driven DesignBehavior
StrategyDecisionAssumptionsHypothesis
Domain-Driven DesignBoundariesStrategy
Add more methods