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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration of two people facing each other, speech bubbles and an open interview notebook.
UX Research
User Interviews
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Purposedifferent
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.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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.
Complexitydifferent
LowLowMediumMedium
Timedifferent
15-30 min30–60 min per interview1-4 h1-3 h
Participantsdifferent
2-61 participant per interview3-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Root cause notes, CountermeasuresInterview Notes, Themes, Insight SummaryProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
Root causeIncidentLeanProblem solving
QualitativeResearchCustomerDiscovery
Root causeProblem solvingQualityIncident
Root causeTreeIncidentQuality
Add more methods