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 Opportunity Interview |  Business Strategy GAP Analysis |  Domain Modeling Domain Context Map |  Domain Modeling EventStorming |
|---|---|---|---|---|
Purposedifferent | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | 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. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-60 min je Interview | 1-3 h | 1-3 h | 2-8 h |
Participantsdifferent | 5-12 Interviews | 2-8 | 3-10 | 5-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Gap Matrix, Action Plan, Risk Notes | Domain Context Map, Boundary Notes, Ownership Map | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | StrategyAnalysisPlanning | Domain-Driven DesignContextBoundaries | Domain-Driven DesignEventsDiscoveryWorkshop |