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 |  Product Discovery Opportunity Interview |  Innovation Design Sprint |
|---|---|---|---|---|
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 opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-2 Tage | 1-2 h je Session | 30-60 min je Interview | 4-5 Tage |
Participantsdifferent | 10-50 | Based on research question | 5-12 Interviews | 5-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Usability Issues, Severity List, Recommendations | Interview Notes, Opportunity Themes, Customer Quotes | Prototype, Test Findings, Decision Rationale |
Tagsno overlap | SatisfactionPrioritizationCustomer | ValidationUXPrototype | DiscoveryInterviewsOpportunityCustomer | Design sprintPrototypeValidationInnovation |