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 |
|---|---|---|---|
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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 20-45 min | 1-3 h | 45-90 min |
Participantsdifferent | 3-12 | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Lessons learned, Action items, Event summary | Domain Context Map, Boundary Notes, Ownership Map | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | LearningOperationsImprovement | Domain-Driven DesignContextBoundaries | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
