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 for Diary Study.
UX Research
Diary Study
Paper illustration of a branching category tree with a highlighted search path and possible dead ends.
UX Research
Tree Testing
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Purposedifferent
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 a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination.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.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-4 Wochen1-2 Tage1-3 h2-6 h
Participantsdifferent
5-20Based on research question2-82-8
Formatdifferent
AsyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelineFindability Metrics, Path Analysis, Revised IAContext Map, Integration Patterns, Boundary NotesEvent Model, UI Flow, Commands, Read Models
Tagsno overlap
UX researchTrackingBehavior
Information architectureNavigationFindability
Domain-Driven DesignBoundariesStrategy
EventsBlueprintDomain-Driven DesignBehavior
Add more methods