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 Contextual Inquiry |  Domain Modeling Context Map |  Product Discovery Opportunity Scoring |
|---|---|---|---|---|
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 work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When opportunities need ranking by their effect, it makes importance and satisfaction directly comparable. It separates problem, assumption, solution, and evidence. The result is captured as an opportunity-score table and top outcomes. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen | 1-3 Wochen | 1-3 h | 60-120 min |
Participantsdifferent | 5-12 Interviews | 4-12 Beobachtungen | 2-8 | 3-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Field Notes, Workflow Insights, Pain Points | Context Map, Integration Patterns, Boundary Notes | Opportunity Score Table, Top Outcomes |
Tagsno overlap | CustomerOutcomesNeeds | UX researchObservationContext | Domain-Driven DesignBoundariesStrategy | PrioritizationDiscoveryOutcomesNeeds |