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
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
Paper illustration showing three sorted card stacks and an open question about a possible group.
UX Research
Card Sorting
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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 an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.When content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations.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
MediumHighLowLow
Timedifferent
1-2 Tage2-6 h20-45 min15-30 min
Participantsdifferent
Based on research question3-10Based on research question2-6
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Findability Metrics, Path Analysis, Revised IAEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsContent groups, Label set, IA hypothesesRoot cause notes, Countermeasures
Tagsno overlap
Information architectureNavigationFindability
CausalityIncidentRoot causeTimeline
Information architectureNavigationStructure
Root causeIncidentLeanProblem solving
Add more methods