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 InnovationARID (Active Reviews for Intermediate Designs)Design Thinking
| Criterion |  Architecture Quality Attribute Workshop |  Product Discovery Outcome-Driven Innovation |  Architecture ARID (Active Reviews for Intermediate Designs) |  Innovation Design Thinking |
|---|---|---|---|---|
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. | 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 complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | 2-4 h | Mehrere Wochen | 2–4 h review as a planning range; preparation and evaluation additional | 1 Tag bis mehrere Wochen |
Participantsdifferent | 5-15 | 2-6 researchers plus sample | Designers, developers as users, and facilitation | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | 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 | Problem Statement, Prototype, Test Learnings |
Tagsno overlap | RequirementsArchitectureWorkshop | OutcomesInnovationResearchQuantitative | ArchitectureEngineeringFeedbackValidationTasks | InnovationPrototypeResearch |