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)Outcome-Driven InnovationSAAM (Software Architecture Analysis Method)Design Sprint
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Outcome-Driven Innovation |  Architecture SAAM (Software Architecture Analysis Method) |  Innovation Design Sprint |
|---|---|---|---|---|
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. | 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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. |
Complexitydifferent | Medium | High | High | High |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | Mehrere Wochen | Preparation, scenario analysis, and findings review; effort depends on scope | 4-5 Tage |
Participantsdifferent | Designers, developers as users, and facilitation | 2-6 researchers plus sample | Architecture experts and stakeholders for scenarios and weighting | 5-8 |
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 | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Prototype, Test Findings, Decision Rationale |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | OutcomesInnovationResearchQuantitative | ArchitectureChangeAnalysisComparisonQuality | Design sprintPrototypeValidationInnovation |