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 |  Knowledge Modeling Teach-back |  Domain Modeling Bounded Context Canvas |  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. | Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations. | 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. | 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 | Medium | Low |
Timedifferent | 1-3 h | 5-20 min | 1-3 h | 45–75 min |
Participantsdifferent | 2-8 | 2-8 | 3-8 | Team members involved |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Understanding Check, Clarification Notes, Learning Gaps | Context Canvas, Glossary, Integration Notes | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | LearningUnderstandingCommunication | Domain-Driven DesignBoundariesModeling | RetrospectiveLearningReflectionTeam |