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 |  Operations After-Action Review |  UX Research HEART Framework |
|---|---|---|---|
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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-2 Tage | 20-45 min | 120 min initial, dann laufend |
Participantsdifferent | 10-50 | 3-12 | 3-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Lessons learned, Action items, Event summary | HEART-GSM Table, Dashboard |
Tagsno overlap | SatisfactionPrioritizationCustomer | LearningOperationsImprovement | MetricsUX researchMeasurementSatisfaction |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
