View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Design Thinking |  UX Research Surveys |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | High | Medium | High |
Timedifferent | 1 Tag bis mehrere Wochen | 3-14 Tage | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 4-10 | 50+ | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Problem Statement, Prototype, Test Learnings | Survey Results, Charts, Segment Insights | 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 |
Tagsno overlap | InnovationPrototypeResearch | QuantitativeResearchValidation | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
