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 Root Cause 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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 | Medium | Low |
Timedifferent | 20-45 min | 30 min Setup, dann laufend | 1-4 h | 15-30 min |
Participantsdifferent | Based on research question | 1-3 maintaining, briefing for everyone | 3-8 | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Content groups, Label set, IA hypotheses | RAID Log, Status Report Source | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Root cause notes, Countermeasures |
Tagsno overlap | Information architectureNavigationStructure | RiskTrackingStakeholdersGovernance | Root causeProblem solvingQualityIncident | Root causeIncidentLeanProblem solving |