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 Contextual Inquiry |  Product Discovery Kano Model |  Operations Root Cause Analysis |
|---|---|---|---|
Purposedifferent | When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen | 1-2 Tage | 1-4 h |
Participantsdifferent | 4-12 Beobachtungen | 10-50 | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Kano Matrix, Feature Classes, Priority Themes | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | UX researchObservationContext | SatisfactionPrioritizationCustomer | Root causeProblem solvingQualityIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
