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 Bounded Context Canvas | ![]() Operations Weekly Review | ![]() Domain Modeling Context Map |
|---|---|---|---|---|
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 business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-3 h | 30-60 min | 1-3 h |
Participantsdifferent | 2-8 | 3-8 | 1 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Context Canvas, Glossary, Integration Notes | Updated Task System, Weekly Focus, Next Actions | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | StrategyAnalysisPlanning | Domain-Driven DesignBoundariesModeling | ProductivityExecutionPlanning | Domain-Driven DesignBoundariesStrategy |



