View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Quality Attribute WorkshopOutcome-Driven InnovationDesign SprintARID (Active Reviews for Intermediate Designs)
| Criterion |  Architecture Quality Attribute Workshop |  Product Discovery Outcome-Driven Innovation |  Innovation Design Sprint |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
Purposedifferent | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | 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. | 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. | 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. |
Complexitydifferent | Medium | High | High | Medium |
Timedifferent | 2-4 h | Mehrere Wochen | 4-5 Tage | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 5-15 | 2-6 researchers plus sample | 5-8 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Prototype, Test Findings, Decision Rationale | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | RequirementsArchitectureWorkshop | OutcomesInnovationResearchQuantitative | Design sprintPrototypeValidationInnovation | ArchitectureEngineeringFeedbackValidationTasks |