View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Affinity DiagrammingArchitecture Decision RecordLASR (Lightweight Approach for Software Reviews)
| Criterion |  UX Research Affinity Diagramming |  Architecture Architecture Decision Record |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 45–90 min | 15-45 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 3-10 | 1-3 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | ADR File, Decision Log, Rationale | 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 |
Tagsno overlap | SynthesisQualitativeRoot cause | ArchitectureRationaleDocumentationGovernance | ArchitectureQualityRiskAssessmentLean |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
