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 Tree Testing | ![]() UX Research Usability Testing |
|---|---|---|---|
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 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 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 1-2 Tage | 1-2 h je Session |
Participantsdifferent | 10-50 | Based on research question | Based on research question |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Findability Metrics, Path Analysis, Revised IA | Usability Issues, Severity List, Recommendations |
Tagsno overlap | SatisfactionPrioritizationCustomer | Information architectureNavigationFindability | ValidationUXPrototype |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






