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 Assumption Mapping |  Growth A/B Testing |
|---|---|---|---|---|
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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | 2-4 h | Mehrere Wochen | 45-60 min | 1-4 Wochen |
Participantsdifferent | 5-15 | 2-6 researchers plus sample | 2-8 | 1-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Assumption map, Test backlog, Risk ranking | Experiment results, Decision log, Learning summary |
Tagsno overlap | RequirementsArchitectureWorkshop | OutcomesInnovationResearchQuantitative | AssumptionsRiskExperimentsValidation | ExperimentsGrowthAnalyticsValidation |