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
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.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
MediumLowMediumLow
Timedifferent
2-6 h45-90 min30-90 min1-2 h
Participantsdifferent
2-82-81-62-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsAssumption List, Critical Assumptions, Learning PlanDecision Tree, Option Map, Assumption ListDIBB document, Belief list, Bet list, Learning report
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
AssumptionsRiskDecisionDiscovery
DecisionTreeOptions
StrategyDecisionAssumptionsHypothesis
Add more methods