View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Tree Testing |  Product Discovery Outcome-Driven Innovation |  Product Discovery Jobs to Be Done |  Innovation Design Thinking |
|---|---|---|---|---|
Purposedifferent | 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 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. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | 1-2 Tage | Mehrere Wochen | 1-3 Wochen | 1 Tag bis mehrere Wochen |
Participantsdifferent | Based on research question | 2-6 researchers plus sample | 5-12 Interviews | 4-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Findability Metrics, Path Analysis, Revised IA | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Job Stories, Outcome Statements, Opportunity List | Problem Statement, Prototype, Test Learnings |
Tagsno overlap | Information architectureNavigationFindability | OutcomesInnovationResearchQuantitative | CustomerOutcomesNeeds | InnovationPrototypeResearch |