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 ALPEN Method
Operations
ALPEN Method
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
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.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.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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung10-20 min daily30-90 min30-90 min
Participantsdifferent
3-20 Reviewer12-81-6
Formatdifferent
AsyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsDaily Plan, Time Estimates, Review NotesConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesDecision Tree, Option Map, Assumption List
Tagsno overlap
ArchitectureDecisionAsyncGovernance
PlanningTime managementProductivityOperations
ConstraintsDecisionPlanningOptions
DecisionTreeOptions
Add more methods