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 Tree Testing |  Operations Causal Factor Analysis |  Operations 5 Whys |  Operations A3 Problem Solving |
|---|---|---|---|---|
Purposedifferent | When a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination. | For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-2 Tage | 2-6 h | 15-30 min | 45-90 min |
Participantsdifferent | Based on research question | 3-10 | 2-6 | 2-5 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Findability Metrics, Path Analysis, Revised IA | Event Timeline, Causal Factor Chart, Cause List, Corrective Actions | Root cause notes, Countermeasures | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | Information architectureNavigationFindability | CausalityIncidentRoot causeTimeline | Root causeIncidentLeanProblem solving | LeanProblem solvingCoachingOperations |