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
Six paper cards show a person moving from a problem through a service flow to a completed outcome.
UX Design
Storyboarding
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
When a usage scenario needs to become understandable early, it condenses situations, context, and flow into a legible sequence. It helps check concept ideas before anything gets built.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.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.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.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
30-90 min1-3 h2-6 h1-4 h
Participantsdifferent
1-82-83-103-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Storyboard, Concept Narrative, Testable AssumptionsCause Tree, Evidence Notes, CountermeasuresFMEA Table, Risk Priority, Mitigation ActionsProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
VisualizationConceptsSequencePrototype
Root causeTreeIncidentQuality
RiskQualityOperationsRoot cause
Root causeProblem solvingQualityIncident
Add more methods