View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Quality Attribute Workshop |  Product Discovery Outcome-Driven Innovation |  Product Discovery Context Canvas |  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. | When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | 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 | Low | High |
Timedifferent | 2-4 h | Mehrere Wochen | 45-90 min | 1 Tag bis mehrere Wochen |
Participantsdifferent | 5-15 | 2-6 researchers plus sample | 3-10 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Context canvas, Open questions, Shared context notes | Problem Statement, Prototype, Test Learnings |
Tagsno overlap | RequirementsArchitectureWorkshop | OutcomesInnovationResearchQuantitative | ContextFramingRequirementsCanvas | InnovationPrototypeResearch |