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 | ![]() Operations Family Tree Analysis | ![]() Operations 5 Whys |
|---|---|---|---|---|
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. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 20-45 min | 1-2 Tage | 2-4 h | 15-30 min |
Participantsdifferent | Based on research question | Based on research question | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Content groups, Label set, IA hypotheses | Findability Metrics, Path Analysis, Revised IA | Family Tree Diagram, Pattern Notes, Systemic Measures | Root cause notes, Countermeasures |
Tagsno overlap | Information architectureNavigationStructure | Information architectureNavigationFindability | Root causePatternsIncidentSystemic | Root causeIncidentLeanProblem solving |



