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 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.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.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
MediumLowLowLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung30-90 min30-60 min10-20 min daily
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 BoundariesUpdated Task System, Weekly Focus, Next ActionsDaily Plan, Time Estimates, Review Notes
Tagsno overlap
ArchitectureDecisionAsyncGovernance
ConstraintsDecisionPlanningOptions
ProductivityExecutionPlanning
PlanningTime managementProductivityOperations
Add more methods