View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Funnel AnalysisRisk StormingATAM (Architecture Tradeoff Analysis Method)ARID (Active Reviews for Intermediate Designs)
| Criterion |  Growth Funnel Analysis |  Architecture Risk Storming |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 60-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1-5 | 4-12 | Evaluation team, architects, and relevant stakeholders | Designers, developers as users, and facilitation |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Funnel report, Drop-off analysis, Optimization hypotheses | Annotated Diagram, Prioritized Risk List, Action Backlog | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | AnalyticsConversionGrowth | RiskArchitectureWorkshopValidation | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureEngineeringFeedbackValidationTasks |