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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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)
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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
1-2 h je Session60-120 min1-4 Wochen2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
Based on research question2-81-6Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Usability Issues, Severity List, RecommendationsCommunication Canvas, Stakeholder Messages, Architecture Communication PlanExperiment results, Decision log, Learning summaryPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
ValidationUXPrototype
ArchitectureCommunicationStakeholdersCanvas
ExperimentsGrowthAnalyticsValidation
ArchitectureEngineeringFeedbackValidationTasks
Add more methods