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 Runbook | ![]() Operations Weekly Review | ![]() Operations Eat the Frog |
|---|---|---|---|---|
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. | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | 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 method protects energy and attention for the task that creates the largest progress and is often postponed. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-45 min | 20-60 min | 30-60 min | 15-90 min daily |
Participantsdifferent | 1-3 | 1-4 | 1 | 1 |
Formatsame | Async | Async | Async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Runbook, Checklist, Escalation Path | Updated Task System, Weekly Focus, Next Actions | Priority Task, Completion Note, Daily Focus |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | OperationsReliabilityDocumentation | ProductivityExecutionPlanning | PrioritizationProductivityFocusExecution |



