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 Weekly Review |  Domain Modeling Context Map |  Architecture arc42 |  Operations Getting Things Done |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | Low | Medium | Low | Medium |
Timedifferent | 30-60 min | 1-3 h | 1-2 Tage | 1-2 h Setup, laufend |
Participantsdifferent | 1 | 2-8 | 1-4 | 1 |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | Updated Task System, Weekly Focus, Next Actions | Context Map, Integration Patterns, Boundary Notes | Architecture Document, Context View, Runtime View, Deployment View | Action Lists, Project List, Review Routine |
Tagsno overlap | ProductivityExecutionPlanning | Domain-Driven DesignBoundariesStrategy | ArchitectureDocumentationCommunication | ProductivityPlanningTasksExecution |