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 Process Mapping |  Engineering Goal Question Metric |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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. | 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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 h | 90-180 min | 1-2 h |
Participantsdifferent | 2-8 | 3-10 | 3-6 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Process Map, Handoff List, Improvement Backlog | GQM Table, Metric Profiles | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ProcessOperationsImprovement | MetricsMeasurementEngineeringAlignment | AlignmentStakeholdersStrategyFacilitation |