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 |  Facilitation Stakeholder Salience Model |  Operations Weekly Review |  Operations Getting Things Done |
|---|---|---|---|---|
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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 60-90 min | 30-60 min | 1-2 h Setup, laufend |
Participantsdifferent | 2-8 | 3-6 | 1 | 1 |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Salience Diagram, Strategy per Class | Updated Task System, Weekly Focus, Next Actions | Action Lists, Project List, Review Routine |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | StakeholdersFacilitationAlignmentGovernance | ProductivityExecutionPlanning | ProductivityPlanningTasksExecution |