View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Domain Modeling Context Map |  Operations Getting Things Done |  Operations Weekly Review |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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 | Low | Medium | Medium | Low |
Timedifferent | 15-45 min | 1-3 h | 1-2 h Setup, laufend | 30-60 min |
Participantsdifferent | 1-3 | 2-8 | 1 | 1 |
Formatdifferent | Async | Workshop + async | Async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Context Map, Integration Patterns, Boundary Notes | Action Lists, Project List, Review Routine | Updated Task System, Weekly Focus, Next Actions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Domain-Driven DesignBoundariesStrategy | ProductivityPlanningTasksExecution | ProductivityExecutionPlanning |