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 |  Agile ROAM Board |  Operations Failure Mode and Effects 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. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 1-4 Wochen | 2-6 h | 20-40 min initial, dann laufend | 2-6 h |
Participantsdifferent | 5-20 | 3-8 | 3-15 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | ROAM Board, Owner List | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | UX researchTrackingBehavior | RiskRoot causeSafety | RiskAgileTrackingAlignment | RiskQualityOperationsRoot cause |