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 Root Cause 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | High | Low | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 45–90 min | 1-4 h |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-10 | 3-8 |
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 | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | SynthesisQualitativeRoot cause | Root causeProblem solvingQualityIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
