View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Growth Funnel Analysis |  Architecture Risk Storming |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h | 60-90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-5 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Funnel report, Drop-off analysis, Optimization hypotheses | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | AnalyticsConversionGrowth | RiskArchitectureWorkshopValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
