View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Outcome-Driven InnovationARID (Active Reviews for Intermediate Designs)Risk StormingATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Product Discovery Outcome-Driven Innovation |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Risk Storming |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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. | 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. |
Complexitydifferent | High | Medium | Low | High |
Timedifferent | Mehrere Wochen | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-6 researchers plus sample | Designers, developers as users, and facilitation | 4-12 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | 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 |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureEngineeringFeedbackValidationTasks | RiskArchitectureWorkshopValidation | ArchitectureQualityRiskTradeoffsStakeholders |