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 of a Lean Canvas with nine fields, notes, and one highlighted learning risk.
Product Strategy
Lean Canvas
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 Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
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 an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable.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 a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-2 Tage45-90 min15-30 min2-4 h
Participantsdifferent
Based on research question1-62-62-6
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Findability Metrics, Path Analysis, Revised IALean Canvas, Core Assumptions, Experiment BacklogRoot cause notes, CountermeasuresBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
Information architectureNavigationFindability
StartupLeanAssumptionsBusiness model
Root causeIncidentLeanProblem solving
Root causeSafetyIncident
Add more methods