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 | ![]() Operations A3 Problem Solving | ![]() Domain Modeling Bounded Context Canvas | ![]() Operations Gemba Walk |
|---|---|---|---|---|
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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 45-90 min | 1-3 h | 30-120 min |
Participantsdifferent | 2-8 | 2-5 | 3-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | A3 Report, Action Plan, Root Cause Analysis | Context Canvas, Glossary, Integration Notes | Observation Notes, Improvement Ideas |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | LeanProblem solvingCoachingOperations | Domain-Driven DesignBoundariesModeling | LeanObservationProcessOperations |



