View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Product Discovery Outcome-Driven Innovation | ![]() Architecture SAAM (Software Architecture Analysis Method) | ![]() UX Research Surveys |
|---|---|---|---|
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. | 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. | When a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal. |
Complexitydifferent | High | High | Medium |
Timedifferent | Mehrere Wochen | Preparation, scenario analysis, and findings review; effort depends on scope | 3-14 Tage |
Participantsdifferent | 2-6 researchers plus sample | Architecture experts and stakeholders for scenarios and weighting | 50+ |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | 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 | Survey Results, Charts, Segment Insights |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureChangeAnalysisComparisonQuality | QuantitativeResearchValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






