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 RAPID
Decision Making
RAPID
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
Paper illustration for DACI
Decision Making
DACI
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 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.When many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung45-90 min1-3 h30-60 min
Participantsdifferent
3-20 Reviewer3-121-52-10
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsRAPID Role Map, Recommendation, Decision LogFunnel report, Drop-off analysis, Optimization hypothesesDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
ArchitectureDecisionAsyncGovernance
DecisionRolesGovernance
AnalyticsConversionGrowth
DecisionRolesGovernanceAlignment
Add more methods