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 Tree Testing | ![]() Operations Family Tree Analysis | ![]() UX Research Card Sorting | ![]() Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-2 Tage | 2-4 h | 20-45 min | Mehrere Tage bis Wochen |
Participantsdifferent | Based on research question | 2-6 | Based on research question | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Findability Metrics, Path Analysis, Revised IA | Family Tree Diagram, Pattern Notes, Systemic Measures | Content groups, Label set, IA hypotheses | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | Information architectureNavigationFindability | Root causePatternsIncidentSystemic | Information architectureNavigationStructure | Root causeSafetySystemicIncident |



