View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations ABC Analysis |  UX Research HEART Framework |  UX Research Contextual Inquiry |  Product Discovery Kano Model |
|---|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30-60 min | 120 min initial, dann laufend | 1-3 Wochen | 1-2 Tage |
Participantsdifferent | 1-5 | 3-6 | 4-12 Beobachtungen | 10-50 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ABC Classification, Focus Rules, Control List | HEART-GSM Table, Dashboard | Field Notes, Workflow Insights, Pain Points | Kano Matrix, Feature Classes, Priority Themes |
Tagsno overlap | PrioritizationOperationsPortfolio | MetricsUX researchMeasurementSatisfaction | UX researchObservationContext | SatisfactionPrioritizationCustomer |