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 Weekly Review.
Operations
Weekly Review
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 ALPEN Method
Operations
ALPEN Method
Purposedifferent
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.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.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.
Complexitydifferent
LowMediumMediumLow
Timedifferent
30-60 min45-90 min1-3 Wochen vom Draft bis zur Entscheidung10-20 min daily
Participantsdifferent
13-123-20 Reviewer1
Formatdifferent
AsyncWorkshop + asyncAsyncAsync
Outputdifferent
Updated Task System, Weekly Focus, Next ActionsRAPID Role Map, Recommendation, Decision LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsDaily Plan, Time Estimates, Review Notes
Tagsno overlap
ProductivityExecutionPlanning
DecisionRolesGovernance
ArchitectureDecisionAsyncGovernance
PlanningTime managementProductivityOperations
Add more methods