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 an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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 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.
Complexitydifferent
LowLowMediumLow
Timedifferent
45-90 min30–60 min per interview1-4 h15-30 min
Participantsdifferent
2-81 participant per interview3-82-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Assumption List, Critical Assumptions, Learning PlanInterview Notes, Themes, Insight SummaryProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanRoot cause notes, Countermeasures
Tagsno overlap
AssumptionsRiskDecisionDiscovery
QualitativeResearchCustomerDiscovery
Root causeProblem solvingQualityIncident
Root causeIncidentLeanProblem solving
Add more methods