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 Outcome-Driven Innovation | ![]() UX Research Card Sorting |
|---|---|---|---|---|
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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | When content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-3 Wochen | 1-2 Tage | Mehrere Wochen | 20-45 min |
Participantsdifferent | 5-12 Interviews | Based on research question | 2-6 researchers plus sample | Based on research question |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Findability Metrics, Path Analysis, Revised IA | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Content groups, Label set, IA hypotheses |
Tagsno overlap | CustomerOutcomesNeeds | Information architectureNavigationFindability | OutcomesInnovationResearchQuantitative | Information architectureNavigationStructure |



