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 of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Purposedifferent
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.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 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.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
LowMediumMediumLow
Timedifferent
45-90 min2-6 h1-3 h1-2 h
Participantssame
2-82-82-82-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Assumption List, Critical Assumptions, Learning PlanEvent Model, UI Flow, Commands, Read ModelsContext Map, Integration Patterns, Boundary NotesDIBB document, Belief list, Bet list, Learning report
Tagsno overlap
AssumptionsRiskDecisionDiscovery
EventsBlueprintDomain-Driven DesignBehavior
Domain-Driven DesignBoundariesStrategy
StrategyDecisionAssumptionsHypothesis
Add more methods