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 illustration for RAPID
Decision Making
RAPID
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Weekly Review.
Operations
Weekly Review
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Purposedifferent
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 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 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.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
MediumMediumLowMedium
Timedifferent
45-90 min1-3 Wochen vom Draft bis zur Entscheidung30-60 min1-2 h Setup, laufend
Participantsdifferent
3-123-20 Reviewer11
Formatdifferent
Workshop + asyncAsyncAsyncAsync
Outputdifferent
RAPID Role Map, Recommendation, Decision LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsUpdated Task System, Weekly Focus, Next ActionsAction Lists, Project List, Review Routine
Tagsno overlap
DecisionRolesGovernance
ArchitectureDecisionAsyncGovernance
ProductivityExecutionPlanning
ProductivityPlanningTasksExecution
Add more methods