View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:5-Minuten VC-CheckATAM (Architecture Tradeoff Analysis Method)ARID (Active Reviews for Intermediate Designs)Risk Storming
| Criterion |  Business Strategy 5-Minuten VC-Check |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list. | 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. | 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 | Low | High | Medium | Low |
Timedifferent | 5-15 min | Several meetings plus preparation and analysis; total effort depends on scope | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min |
Participantsdifferent | 1-5 | Evaluation team, architects, and relevant stakeholders | Designers, developers as users, and facilitation | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step | 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 | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | StartupValidationCompetition | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureEngineeringFeedbackValidationTasks | RiskArchitectureWorkshopValidation |