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 MORT Analysis |  UX Research Affinity Diagramming |  Operations 5 Whys |
|---|---|---|---|---|
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. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 1-2 Tage | Mehrere Tage bis Wochen | 45–90 min | 15-30 min |
Participantsdifferent | 10-50 | 2-6 | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Theme clusters, Insight statements, Opportunity areas | Root cause notes, Countermeasures |
Tagsno overlap | SatisfactionPrioritizationCustomer | Root causeSafetySystemicIncident | SynthesisQualitativeRoot cause | Root causeIncidentLeanProblem solving |