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 a branching category tree with a highlighted search path and possible dead ends.
UX Research
Tree Testing
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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)
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
When a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.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.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.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
1-2 Tage15-30 min3–4 h for initial assessment; preparation and deeper analysis additional2-6 h
Participantsdifferent
Based on research question2-61 or a small team; particularly suitable for 3–4 people3-10
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Findability Metrics, Path Analysis, Revised IARoot cause notes, CountermeasuresLean 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 checksFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
Information architectureNavigationFindability
Root causeIncidentLeanProblem solving
ArchitectureQualityRiskAssessmentLean
RiskQualityOperationsRoot cause
Add more methods