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 A3 Problem Solving |  Operations 5 Whys |
|---|---|---|---|---|
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 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. | 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 | Medium | Medium | Low |
Timedifferent | 1-3 Wochen | 1-2 Tage | 45-90 min | 15-30 min |
Participantsdifferent | 4-12 Beobachtungen | 10-50 | 2-5 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Kano Matrix, Feature Classes, Priority Themes | A3 Report, Action Plan, Root Cause Analysis | Root cause notes, Countermeasures |
Tagsno overlap | UX researchObservationContext | SatisfactionPrioritizationCustomer | LeanProblem solvingCoachingOperations | Root causeIncidentLeanProblem solving |