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 a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
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.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitysame
MediumMediumMedium
Timedifferent
2-6 h1-4 Wochen45-60 min
Participantsdifferent
2-85-202-8
Formatdifferent
Workshop + asyncAsyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsDiary Entries, Longitudinal Patterns, Experience TimelineAssumption map, Test backlog, Risk ranking
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
UX researchTrackingBehavior
AssumptionsRiskExperimentsValidation
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption Test
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming