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 illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
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.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.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.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
MediumLowMediumLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung30-90 min1-2 h Setup, laufend30-60 min
Participantsdifferent
3-20 Reviewer2-811
Formatdifferent
AsyncWorkshop + asyncAsyncAsync
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesAction Lists, Project List, Review RoutineUpdated Task System, Weekly Focus, Next Actions
Tagsno overlap
ArchitectureDecisionAsyncGovernance
ConstraintsDecisionPlanningOptions
ProductivityPlanningTasksExecution
ProductivityExecutionPlanning
Add more methods