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 Request for Comments |  Operations Time Blocking |  Operations Eat the Frog |  Operations Getting Things Done |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure. | The method protects energy and attention for the task that creates the largest progress and is often postponed. | 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 | Low | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 15-30 min Planung, laufend | 15-90 min daily | 1-2 h Setup, laufend |
Participantsdifferent | 3-20 Reviewer | 1 | 1 | 1 |
Formatsame | Async | Async | Async | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Blocked Calendar, Capacity View, Focus Plan | Priority Task, Completion Note, Daily Focus | Action Lists, Project List, Review Routine |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | PlanningTime managementFocus | PrioritizationProductivityFocusExecution | ProductivityPlanningTasksExecution |