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 Context Map | ![]() Architecture Architecture Decision Record |
|---|---|---|---|
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 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 h | 1-3 h | 15-45 min |
Participantsdifferent | 2-8 | 2-8 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Context Map, Integration Patterns, Boundary Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | StrategyAnalysisPlanning | Domain-Driven DesignBoundariesStrategy | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






