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 Contextual Inquiry.
UX Research
Contextual Inquiry
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of a branching category tree with a highlighted search path and possible dead ends.
UX Research
Tree Testing
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Purposedifferent
When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise.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 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 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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 Wochen2-6 h1-2 Tage1-3 h
Participantsdifferent
4-12 Beobachtungen2-8Based on research question3-10
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Field Notes, Workflow Insights, Pain PointsEvent Model, UI Flow, Commands, Read ModelsFindability Metrics, Path Analysis, Revised IADomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
UX researchObservationContext
EventsBlueprintDomain-Driven DesignBehavior
Information architectureNavigationFindability
Domain-Driven DesignContextBoundaries
Add more methods