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 of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Weekly Review.
Operations
Weekly Review
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 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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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
MediumMediumMediumLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung1-2 h Setup, laufend1-3 h30-60 min
Participantsdifferent
3-20 Reviewer11-81
Formatdifferent
AsyncAsyncWorkshop + asyncAsync
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsAction Lists, Project List, Review RoutineArgument Map, Evidence Gaps, Decision RationaleUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
ArchitectureDecisionAsyncGovernance
ProductivityPlanningTasksExecution
SensemakingDecisionRationale
ProductivityExecutionPlanning
Add more methods