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 of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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.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 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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
45-90 min1-3 Wochen vom Draft bis zur Entscheidung1-3 h1-4 Wochen
Participantsdifferent
3-123-20 Reviewer1-51-6
Formatdifferent
Workshop + asyncAsyncAsyncAsync
Outputdifferent
RAPID Role Map, Recommendation, Decision LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsFunnel report, Drop-off analysis, Optimization hypothesesExperiment results, Decision log, Learning summary
Tagsno overlap
DecisionRolesGovernance
ArchitectureDecisionAsyncGovernance
AnalyticsConversionGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods