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 Dual-Track Agile | ![]() Product Discovery Kano Model | ![]() Product Discovery Jobs to Be Done | ![]() Delivery Cost of Delay |
|---|---|---|---|---|
Purposedifferent | 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 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 switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | Laufend, Wochen bis Monate | 1-2 Tage | 1-3 Wochen | 90-180 min |
Participantsdifferent | 4-10 | 10-50 | 5-12 Interviews | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Kano Matrix, Feature Classes, Priority Themes | Job Stories, Outcome Statements, Opportunity List | CoD Table, Prioritization Sequence |
Tagsno overlap | AgileDiscoveryDelivery | SatisfactionPrioritizationCustomer | CustomerOutcomesNeeds | PrioritizationDeliveryEconomicsDecision |



