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 |  Operations Fault Tree Analysis |  Delivery RAID Log |  Operations MORT 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. | 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. | 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. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 1-4 Wochen | 2-6 h | 30 min Setup, dann laufend | Mehrere Tage bis Wochen |
Participantsdifferent | 5-20 | 3-8 | 1-3 maintaining, briefing for everyone | 2-6 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | RAID Log, Status Report Source | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | UX researchTrackingBehavior | RiskRoot causeSafety | RiskTrackingStakeholdersGovernance | Root causeSafetySystemicIncident |