View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research Card Sorting | ![]() UX Research Tree Testing | ![]() Knowledge Modeling Event Modeling | ![]() Domain Modeling EventStorming |
|---|---|---|---|---|
Purposedifferent | When content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations. | 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. | 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 domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 20-45 min | 1-2 Tage | 2-6 h | 2-8 h |
Participantsdifferent | Based on research question | Based on research question | 2-8 | 5-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Content groups, Label set, IA hypotheses | Findability Metrics, Path Analysis, Revised IA | Event Model, UI Flow, Commands, Read Models | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | Information architectureNavigationStructure | Information architectureNavigationFindability | EventsBlueprintDomain-Driven DesignBehavior | Domain-Driven DesignEventsDiscoveryWorkshop |



