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 |  Domain Modeling EventStorming |  Business Strategy GAP 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 domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen | 2-8 h | 1-3 h |
Participantsdifferent | 5-12 Interviews | 5-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Gap Matrix, Action Plan, Risk Notes |
Tagsno overlap | CustomerOutcomesNeeds | Domain-Driven DesignEventsDiscoveryWorkshop | StrategyAnalysisPlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
