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 Change Analysis | ![]() Operations Failure Mode and Effects Analysis | ![]() 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. | 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 | Medium | High | High |
Timedifferent | 1-4 Wochen | 45-120 min | 2-6 h | 2-6 h |
Participantsdifferent | 5-20 | 2-6 | 3-10 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Change Matrix, Cause Hypotheses, Validation Questions, Action List | FMEA Table, Risk Priority, Mitigation Actions | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions |
Tagsno overlap | UX researchTrackingBehavior | ChangeRoot causeTroubleshootingComparison | RiskQualityOperationsRoot cause | RiskRoot causeSafety |



