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 |  Innovation TRIZ |  Operations Root Cause Analysis |  Operations 5 Whys |
|---|---|---|---|---|
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 technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-2 Tage | 1-4 h | 1-4 h | 15-30 min |
Participantsdifferent | Based on research question | 2-8 | 3-8 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Findability Metrics, Path Analysis, Revised IA | Contradiction Statement, Inventive Principles, Solution Concepts | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Root cause notes, Countermeasures |
Tagsno overlap | Information architectureNavigationFindability | InnovationProblem solvingContradictionsCreativity | Root causeProblem solvingQualityIncident | Root causeIncidentLeanProblem solving |