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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.
Complexitydifferent
MediumHighMediumHigh
Timedifferent
1-2 h je Session1-4 Wochen2–4 h review as a planning range; preparation and evaluation additional4-5 Tage
Participantsdifferent
Based on research question1-6Designers, developers as users, and facilitation5-8
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Usability Issues, Severity List, RecommendationsExperiment results, Decision log, Learning summaryPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsPrototype, Test Findings, Decision Rationale
Tags1 shared
ValidationUXPrototype
ExperimentsGrowthAnalyticsValidation
ArchitectureEngineeringFeedbackValidationTasks
Design sprintPrototypeValidationInnovation
Add more methods