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 for Weekly Review.
Operations
Weekly Review
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 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.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.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
MediumLowMediumLow
Timedifferent
45-90 min30-60 min1-3 Wochen vom Draft bis zur Entscheidung10-20 min daily
Participantsdifferent
3-1213-20 Reviewer1
Formatdifferent
Workshop + asyncAsyncAsyncAsync
Outputdifferent
RAPID Role Map, Recommendation, Decision LogUpdated Task System, Weekly Focus, Next ActionsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsDaily Plan, Time Estimates, Review Notes
Tagsno overlap
DecisionRolesGovernance
ProductivityExecutionPlanning
ArchitectureDecisionAsyncGovernance
PlanningTime managementProductivityOperations
Add more methods