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 |  Delivery RAID Log |  Operations MORT 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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 | Low | High | Low |
Timedifferent | 20-45 min | 30 min Setup, dann laufend | Mehrere Tage bis Wochen | 15-30 min |
Participantsdifferent | Based on research question | 1-3 maintaining, briefing for everyone | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Content groups, Label set, IA hypotheses | RAID Log, Status Report Source | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Root cause notes, Countermeasures |
Tagsno overlap | Information architectureNavigationStructure | RiskTrackingStakeholdersGovernance | Root causeSafetySystemicIncident | Root causeIncidentLeanProblem solving |