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 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
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
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.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.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.
Complexitydifferent
MediumLowLowHigh
Timedifferent
1-2 Tage20-45 min15-30 min1-6 Wochen
Participantsdifferent
Based on research questionBased on research question2-64-10
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Findability Metrics, Path Analysis, Revised IAContent groups, Label set, IA hypothesesRoot cause notes, Countermeasures8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
Information architectureNavigationFindability
Information architectureNavigationStructure
Root causeIncidentLeanProblem solving
QualityProblem solvingRoot cause
Add more methods