View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:User InterviewsLASR (Lightweight Approach for Software Reviews)SAAM (Software Architecture Analysis Method)Change Analysis
| Criterion |  UX Research User Interviews |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Change Analysis |
|---|---|---|---|---|
Purposedifferent | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | 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 | Low | Medium | High | Medium |
Timedifferent | 30–60 min per interview | 3–4 h for initial assessment; preparation and deeper analysis additional | Preparation, scenario analysis, and findings review; effort depends on scope | 45-120 min |
Participantsdifferent | 1 participant per interview | 1 or a small team; particularly suitable for 3–4 people | Architecture experts and stakeholders for scenarios and weighting | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | 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 | QualitativeResearchCustomerDiscovery | ArchitectureQualityRiskAssessmentLean | ArchitectureChangeAnalysisComparisonQuality | ChangeRoot causeTroubleshootingComparison |