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 5 Whys |  Operations 8D Problem Solving |
|---|---|---|---|---|
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. | 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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-3 Wochen | 1-2 Tage | 15-30 min | 1-6 Wochen |
Participantsdifferent | 4-12 Beobachtungen | 10-50 | 2-6 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Kano Matrix, Feature Classes, Priority Themes | Root cause notes, Countermeasures | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | UX researchObservationContext | SatisfactionPrioritizationCustomer | Root causeIncidentLeanProblem solving | QualityProblem solvingRoot cause |