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 Diary Study |  Delivery RAID Log |  Operations Fishbone Diagram |  Operations Fault Tree Analysis |
|---|---|---|---|---|
Purposedifferent | When experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory. | 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 | Medium | Low | Low | High |
Timedifferent | 1-4 Wochen | 30 min Setup, dann laufend | 30-60 min | 2-6 h |
Participantsdifferent | 5-20 | 1-3 maintaining, briefing for everyone | 2-8 | 3-8 |
Formatdifferent | Async | Async | Workshop | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | RAID Log, Status Report Source | Fishbone Diagram, Cause Categories, Investigation Backlog | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions |
Tagsno overlap | UX researchTrackingBehavior | RiskTrackingStakeholdersGovernance | Root causeQualityOperations | RiskRoot causeSafety |