methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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 complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-2 h Setup, laufend1-3 Wochen vom Draft bis zur Entscheidung45-90 min15-45 min
Participantsdifferent
13-20 Reviewer3-121-3
Formatdifferent
AsyncAsyncWorkshop + asyncAsync
Outputdifferent
Action Lists, Project List, Review RoutineRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsRAPID Role Map, Recommendation, Decision LogADR File, Decision Log, Rationale
Tagsno overlap
ProductivityPlanningTasksExecution
ArchitectureDecisionAsyncGovernance
DecisionRolesGovernance
ArchitectureRationaleDocumentationGovernance
Add more methods