View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Growth Funnel Analysis | ![]() Architecture Request for Comments | ![]() Decision Making Decision Rights Mapping |
|---|---|---|---|
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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min |
Participantsdifferent | 1-5 | 3-20 Reviewer | 4-12 |
Formatdifferent | Async | Async | Workshop |
Outputdifferent | Funnel report, Drop-off analysis, Optimization hypotheses | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement |
Tagsno overlap | AnalyticsConversionGrowth | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






