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 participant using a prototype while an observer takes notes beside a highlighted usability issue.
UX Research
Usability Testing
First-click Testing method illustration showing its working structure
UX Research
First-click Testing
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 product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down.When users immediately turn the wrong way on a screen or wireframe, first click testing checks initial orientation at high speed. The first click shows early whether expectation, labeling, and wayfinding fit together.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 h je Session1-2 Tage15-30 min1-6 Wochen
Participantsdifferent
Based on research question10-302-64-10
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Usability Issues, Severity List, RecommendationsClick Heatmap, Success Rate, Design RecommendationsRoot cause notes, Countermeasures8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
ValidationUXPrototype
UXNavigationFindabilityValidation
Root causeIncidentLeanProblem solving
QualityProblem solvingRoot cause
Add more methods