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 ABC Analysis |  Operations After-Action Review |  Domain Modeling Domain Context Map |  Operations Process Mapping |
|---|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 30-60 min | 20-45 min | 1-3 h | 1-3 h |
Participantsdifferent | 1-5 | 3-12 | 3-10 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ABC Classification, Focus Rules, Control List | Lessons learned, Action items, Event summary | Domain Context Map, Boundary Notes, Ownership Map | Process Map, Handoff List, Improvement Backlog |
Tagsno overlap | PrioritizationOperationsPortfolio | LearningOperationsImprovement | Domain-Driven DesignContextBoundaries | ProcessOperationsImprovement |