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 SAAM (Software Architecture Analysis Method) |  UX Research Affinity Diagramming |  Operations Change Analysis |
|---|---|---|---|
Purposedifferent | 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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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. |
Complexitydifferent | High | Low | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 45–90 min | 45-120 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | 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 | Theme clusters, Insight statements, Opportunity areas | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | SynthesisQualitativeRoot cause | ChangeRoot causeTroubleshootingComparison |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
