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 Risk Storming |  Architecture Architecture Decision Record |  Product Discovery Assumption 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 60-90 min | 15-45 min | 45-60 min |
Participantsdifferent | 1-5 | 4-12 | 1-3 | 2-8 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | Funnel report, Drop-off analysis, Optimization hypotheses | Annotated Diagram, Prioritized Risk List, Action Backlog | ADR File, Decision Log, Rationale | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | AnalyticsConversionGrowth | RiskArchitectureWorkshopValidation | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskExperimentsValidation |