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 |  Innovation Design Sprint |  UX Research Usability Testing |  Product Discovery Wizard of Oz Test |
|---|---|---|---|---|
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 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. | 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 new experience would still be too expensive to automate for real, it simulates the outcome behind the scenes. It checks user reaction and value before the technology disappears. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | 1-2 Tage | 4-5 Tage | 1-2 h je Session | 2-10 Tage |
Participantsdifferent | 10-50 | 5-8 | Based on research question | 5-20 Nutzer |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Prototype, Test Findings, Decision Rationale | Usability Issues, Severity List, Recommendations | Prototype Learnings, Manual Effort Notes, Risk List |
Tagsno overlap | SatisfactionPrioritizationCustomer | Design sprintPrototypeValidationInnovation | ValidationUXPrototype | PrototypeValidationMVP |