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 Tree Testing | ![]() UX Research Card Sorting |
|---|---|---|---|---|
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 a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-2 Tage | 1-2 h je Session | 1-2 Tage | 20-45 min |
Participantsdifferent | 10-50 | Based on research question | Based on research question | Based on research question |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Usability Issues, Severity List, Recommendations | Findability Metrics, Path Analysis, Revised IA | Content groups, Label set, IA hypotheses |
Tagsno overlap | SatisfactionPrioritizationCustomer | ValidationUXPrototype | Information architectureNavigationFindability | Information architectureNavigationStructure |



