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 5 Whys |  Operations A3 Problem Solving |
|---|---|---|---|---|
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 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 20-45 min | 30 min Setup, dann laufend | 15-30 min | 45-90 min |
Participantsdifferent | Based on research question | 1-3 maintaining, briefing for everyone | 2-6 | 2-5 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Content groups, Label set, IA hypotheses | RAID Log, Status Report Source | Root cause notes, Countermeasures | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | Information architectureNavigationStructure | RiskTrackingStakeholdersGovernance | Root causeIncidentLeanProblem solving | LeanProblem solvingCoachingOperations |