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 Domain Context Map |  Operations Process Mapping |  Operations Gemba Walk |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 1-3 h | 30-120 min | 20-45 min |
Participantsdifferent | 3-10 | 3-10 | 2-6 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Process Map, Handoff List, Improvement Backlog | Observation Notes, Improvement Ideas | Lessons learned, Action items, Event summary |
Tagsno overlap | Domain-Driven DesignContextBoundaries | ProcessOperationsImprovement | LeanObservationProcessOperations | LearningOperationsImprovement |