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 for Diary Study.
UX Research
Diary Study
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
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 experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory.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
MediumMediumLowMedium
Timedifferent
2-6 h1-4 Wochen1-2 h1-3 h
Participantsdifferent
2-85-202-82-8
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsDiary Entries, Longitudinal Patterns, Experience TimelineDIBB document, Belief list, Bet list, Learning reportContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
UX researchTrackingBehavior
StrategyDecisionAssumptionsHypothesis
Domain-Driven DesignBoundariesStrategy
Add more methods