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)Change AnalysisSAAM (Software Architecture Analysis Method)
| Criterion |  Product Discovery Outcome-Driven Innovation |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Change Analysis |  Architecture SAAM (Software Architecture 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. |
Complexitydifferent | High | Medium | Medium | High |
Timedifferent | Mehrere Wochen | 2–4 h review as a planning range; preparation and evaluation additional | 45-120 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 2-6 researchers plus sample | Designers, developers as users, and facilitation | 2-6 | Architecture experts and stakeholders for scenarios and weighting |
Formatsame | Workshop + async | Workshop + async | Workshop + async | 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 | Change Matrix, Cause Hypotheses, Validation Questions, Action List | 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 |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureEngineeringFeedbackValidationTasks | ChangeRoot causeTroubleshootingComparison | ArchitectureChangeAnalysisComparisonQuality |