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 |  Product Discovery Dual-Track Agile |  Product Discovery Opportunity 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 uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | Laufend, Wochen bis Monate | 30-60 min je Interview |
Participantsdifferent | 10-50 | 4-10 | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | SatisfactionPrioritizationCustomer | AgileDiscoveryDelivery | DiscoveryInterviewsOpportunityCustomer |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
