View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Runbook |  Growth Funnel Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | 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. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 20-60 min | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 Tage |
Participantsdifferent | 1-4 | 1-5 | Evaluation team, architects, and relevant stakeholders | 1-4 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | Runbook, Checklist, Escalation Path | Funnel report, Drop-off analysis, Optimization hypotheses | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | OperationsReliabilityDocumentation | AnalyticsConversionGrowth | ArchitectureQualityRiskTradeoffsStakeholders | DocumentationStakeholdersArchitecture |