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 5 Whys |  Operations Barrier Analysis |
|---|---|---|---|---|
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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-2 Tage | 120 min initial, dann laufend | 15-30 min | 2-4 h |
Participantsdifferent | 10-50 | 3-6 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | HEART-GSM Table, Dashboard | Root cause notes, Countermeasures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | SatisfactionPrioritizationCustomer | MetricsUX researchMeasurementSatisfaction | Root causeIncidentLeanProblem solving | Root causeSafetyIncident |