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 |  Engineering Goal Question Metric |  UX Research HEART Framework |  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 technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | 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 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 | 90-180 min | 120 min initial, dann laufend | 1-2 Tage |
Participantsdifferent | 1-5 | 3-6 | 3-6 | 10-50 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ABC Classification, Focus Rules, Control List | GQM Table, Metric Profiles | HEART-GSM Table, Dashboard | Kano Matrix, Feature Classes, Priority Themes |
Tagsno overlap | PrioritizationOperationsPortfolio | MetricsMeasurementEngineeringAlignment | MetricsUX researchMeasurementSatisfaction | SatisfactionPrioritizationCustomer |