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 DIBB with its method-specific working model.
Product Strategy
DIBB
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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.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 a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
2-6 h1-2 h1-3 h45-90 min
Participantsdifferent
2-82-83-102-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsDIBB document, Belief list, Bet list, Learning reportDomain Context Map, Boundary Notes, Ownership MapAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
StrategyDecisionAssumptionsHypothesis
Domain-Driven DesignContextBoundaries
AssumptionsRiskDecisionDiscovery
Add more methods