View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Agile Start Stop Continue |  Operations After-Action Review |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 30-60 min | 20-45 min | 45–75 min |
Participantsdifferent | 2-8 | 3-12 | 3-12 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Start Stop Continue Board, Improvement Actions | Lessons learned, Action items, Event summary | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | RetrospectiveImprovementTeamReflection | LearningOperationsImprovement | RetrospectiveLearningReflectionTeam |