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 |  Operations Weekly Review |  Architecture C4 Model |  Operations Getting Things Done |
|---|---|---|---|---|
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. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | Low | Low | Medium |
Timedifferent | 15-45 min | 30-60 min | 1-4 h | 1-2 h Setup, laufend |
Participantsdifferent | 1-3 | 1 | 1-5 | 1 |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Updated Task System, Weekly Focus, Next Actions | Context Diagram, Container Diagram, Component Diagram | Action Lists, Project List, Review Routine |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ProductivityExecutionPlanning | ArchitectureCommunicationVisualization | ProductivityPlanningTasksExecution |