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 Weekly Review |  Business Strategy Strategy Map |  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. | In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable. | A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 30-60 min | 2-4 h workshop plus review | 1-2 h |
Participantsdifferent | 2-8 | 1 | 4-10 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Updated Task System, Weekly Focus, Next Actions | Strategy Map, Objective Set, Cause-Effect Hypotheses | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ProductivityExecutionPlanning | AlignmentExecutionGoalsCausality | AlignmentStakeholdersStrategyFacilitation |