View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Personas |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Change Analysis |
|---|---|---|---|
Purposedifferent | When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | 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. | 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 | Medium | High | Medium |
Timedifferent | 1-3 Tage | Preparation, scenario analysis, and findings review; effort depends on scope | 45-120 min |
Participantsdifferent | Internes Team | Architecture experts and stakeholders for scenarios and weighting | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | 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 | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | ResearchCustomerSynthesis | ArchitectureChangeAnalysisComparisonQuality | ChangeRoot causeTroubleshootingComparison |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
