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 Getting Things Done | ![]() Architecture Request for Comments | ![]() Decision Making Decision Rights Mapping | ![]() Operations Weekly Review |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 1-2 h Setup, laufend | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min | 30-60 min |
Participantsdifferent | 1 | 3-20 Reviewer | 4-12 | 1 |
Formatdifferent | Async | Async | Workshop | Async |
Outputdifferent | Action Lists, Project List, Review Routine | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement | Updated Task System, Weekly Focus, Next Actions |
Tagsno overlap | ProductivityPlanningTasksExecution | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility | ProductivityExecutionPlanning |



