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 |  Domain Modeling EventStorming |  Architecture C4 Model |
|---|---|---|---|
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 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 h | 2-8 h | 1-4 h |
Participantsdifferent | 2-8 | 5-12 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | StrategyAnalysisPlanning | Domain-Driven DesignEventsDiscoveryWorkshop | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
