View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Kano Model |  UX Research HEART Framework |  Operations Gemba Walk |  UX Research Contextual Inquiry |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-2 Tage | 120 min initial, dann laufend | 30-120 min | 1-3 Wochen |
Participantsdifferent | 10-50 | 3-6 | 2-6 | 4-12 Beobachtungen |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | HEART-GSM Table, Dashboard | Observation Notes, Improvement Ideas | Field Notes, Workflow Insights, Pain Points |
Tagsno overlap | SatisfactionPrioritizationCustomer | MetricsUX researchMeasurementSatisfaction | LeanObservationProcessOperations | UX researchObservationContext |