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 Getting Things Done |  Business Strategy Strategy Map |  Operations Weekly Review |
|---|---|---|---|---|
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 many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 1-2 h Setup, laufend | 2-4 h workshop plus review | 30-60 min |
Participantsdifferent | 2-8 | 1 | 4-10 | 1 |
Formatdifferent | Workshop + async | Async | Workshop | Async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Action Lists, Project List, Review Routine | Strategy Map, Objective Set, Cause-Effect Hypotheses | Updated Task System, Weekly Focus, Next Actions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ProductivityPlanningTasksExecution | AlignmentExecutionGoalsCausality | ProductivityExecutionPlanning |