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 Fishbone Diagram |  Operations Fault Tree Analysis |
|---|---|---|---|---|
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 has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. |
Complexitydifferent | Low | Low | Low | High |
Timedifferent | 20-45 min | 30 min Setup, dann laufend | 30-60 min | 2-6 h |
Participantsdifferent | Based on research question | 1-3 maintaining, briefing for everyone | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Content groups, Label set, IA hypotheses | RAID Log, Status Report Source | Fishbone Diagram, Cause Categories, Investigation Backlog | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions |
Tagsno overlap | Information architectureNavigationStructure | RiskTrackingStakeholdersGovernance | Root causeQualityOperations | RiskRoot causeSafety |