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 of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Paper illustration for Weekly Review.
Operations
Weekly Review
Paper illustration for ALPEN Method
Operations
ALPEN Method
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.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.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 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
MediumMediumLowLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung90-180 min30-60 min10-20 min daily
Participantsdifferent
3-20 Reviewer4-1211
Formatdifferent
AsyncWorkshopAsyncAsync
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsDecision Rights Matrix, AgreementUpdated Task System, Weekly Focus, Next ActionsDaily Plan, Time Estimates, Review Notes
Tagsno overlap
ArchitectureDecisionAsyncGovernance
DecisionGovernanceAlignmentResponsibility
ProductivityExecutionPlanning
PlanningTime managementProductivityOperations
Add more methods