methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
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.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.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
LowLowHighMedium
Timedifferent
30–60 min per interview15-45 min2-6 h3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
1 participant per interview1-33-101 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Interview Notes, Themes, Insight SummaryADR File, Decision Log, RationaleFMEA Table, Risk Priority, Mitigation ActionsLean 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
QualitativeResearchCustomerDiscovery
ArchitectureRationaleDocumentationGovernance
RiskQualityOperationsRoot cause
ArchitectureQualityRiskAssessmentLean
Add more methods