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
Funnel Analysis workspace showing the question, observations, and next decision.
Growth
Funnel Analysis
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for DACI
Decision Making
DACI
Purposedifferent
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.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 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.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
MediumMediumHighLow
Timedifferent
1-3 h1-3 Wochen vom Draft bis zur Entscheidung1-4 Wochen30-60 min
Participantsdifferent
1-53-20 Reviewer1-62-10
Formatdifferent
AsyncAsyncAsyncWorkshop + async
Outputdifferent
Funnel report, Drop-off analysis, Optimization hypothesesRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsExperiment results, Decision log, Learning summaryDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
AnalyticsConversionGrowth
ArchitectureDecisionAsyncGovernance
ExperimentsGrowthAnalyticsValidation
DecisionRolesGovernanceAlignment
Add more methods