View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy GAP Analysis |  UX Research User Interviews |  Domain Modeling EventStorming |
|---|---|---|---|
Purposedifferent | 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 teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 h | 30–60 min per interview | 2-8 h |
Participantsdifferent | 2-8 | 1 participant per interview | 5-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Interview Notes, Themes, Insight Summary | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | StrategyAnalysisPlanning | QualitativeResearchCustomerDiscovery | Domain-Driven DesignEventsDiscoveryWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
