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 After-Action Review |  UX Research HEART Framework |  Product Discovery Kano Model |  Operations ABC Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 20-45 min | 120 min initial, dann laufend | 1-2 Tage | 30-60 min |
Participantsdifferent | 3-12 | 3-6 | 10-50 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Lessons learned, Action items, Event summary | HEART-GSM Table, Dashboard | Kano Matrix, Feature Classes, Priority Themes | ABC Classification, Focus Rules, Control List |
Tagsno overlap | LearningOperationsImprovement | MetricsUX researchMeasurementSatisfaction | SatisfactionPrioritizationCustomer | PrioritizationOperationsPortfolio |