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 |  Domain Modeling Domain Context Map |  Decision Making Force Field Analysis |  Domain Modeling 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. | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 | Low | Medium | Low | Medium |
Timedifferent | 20-45 min | 1-3 h | 45-90 min | 1-3 h |
Participantsdifferent | 3-12 | 3-10 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Lessons learned, Action items, Event summary | Domain Context Map, Boundary Notes, Ownership Map | Force Field Map, Change Levers, Risk Notes | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | LearningOperationsImprovement | Domain-Driven DesignContextBoundaries | ChangeDecisionStrategy | Domain-Driven DesignBoundariesStrategy |