View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)Lean CanvasATAM (Architecture Tradeoff Analysis Method)Risk Storming
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Strategy Lean Canvas |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | 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. | When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | 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. | 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 | Medium | Medium | High | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | 1-6 | Evaluation team, architects, and relevant stakeholders | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Lean Canvas, Core Assumptions, Experiment Backlog | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | StartupLeanAssumptionsBusiness model | ArchitectureQualityRiskTradeoffsStakeholders | RiskArchitectureWorkshopValidation |