View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations After-Action Review |  Business Strategy GAP Analysis |  Domain Modeling Context Map |  Domain Modeling Domain Context Map |
|---|---|---|---|---|
Purposedifferent | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 20-45 min | 1-3 h | 1-3 h | 1-3 h |
Participantsdifferent | 3-12 | 2-8 | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Lessons learned, Action items, Event summary | Gap Matrix, Action Plan, Risk Notes | Context Map, Integration Patterns, Boundary Notes | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | LearningOperationsImprovement | StrategyAnalysisPlanning | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignContextBoundaries |