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 Usability Testing |  UX Research Card Sorting |  Product Discovery Solution Interview |
|---|---|---|---|---|
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. | When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down. | When content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations. | When a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-2 Tage | 1-2 h je Session | 20-45 min | 30-60 min je Interview |
Participantsdifferent | 10-50 | Based on research question | Based on research question | 5-10 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Usability Issues, Severity List, Recommendations | Content groups, Label set, IA hypotheses | Solution Feedback, Objection List, Validation Notes |
Tagsno overlap | SatisfactionPrioritizationCustomer | ValidationUXPrototype | Information architectureNavigationStructure | ValidationInterviewsPrototype |