View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Change AnalysisUsability TestingDesign ThinkingSAAM (Software Architecture Analysis Method)
| Criterion | ![]() Operations Change Analysis | ![]() UX Research Usability Testing | ![]() Innovation Design Thinking | ![]() Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down. | 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. | 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 | Medium | Medium | High | High |
Timedifferent | 45-120 min | 1-2 h je Session | 1 Tag bis mehrere Wochen | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 2-6 | Based on research question | 4-10 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Usability Issues, Severity List, Recommendations | Problem Statement, Prototype, Test Learnings | 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 | ChangeRoot causeTroubleshootingComparison | ValidationUXPrototype | InnovationPrototypeResearch | ArchitectureChangeAnalysisComparisonQuality |



