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 Jobs to Be Done |  UX Research Tree Testing |  Product Discovery Kano Model |  Operations ABC Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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 features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Wochen | 1-2 Tage | 1-2 Tage | 30-60 min |
Participantsdifferent | 5-12 Interviews | Based on research question | 10-50 | 1-5 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Findability Metrics, Path Analysis, Revised IA | Kano Matrix, Feature Classes, Priority Themes | ABC Classification, Focus Rules, Control List |
Tagsno overlap | CustomerOutcomesNeeds | Information architectureNavigationFindability | SatisfactionPrioritizationCustomer | PrioritizationOperationsPortfolio |