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 showing three sorted card stacks and an open question about a possible group.
UX Research
Card Sorting
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
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.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.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.
Complexitydifferent
LowHighLowHigh
Timedifferent
20-45 minSeveral meetings plus preparation and analysis; total effort depends on scope1-5 Tage1-4 Wochen
Participantsdifferent
Based on research questionEvaluation team, architects, and relevant stakeholdersNutzertraffic1-6
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncAsync
Outputdifferent
Content groups, Label set, IA hypothesesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
Information architectureNavigationStructure
ArchitectureQualityRiskTradeoffsStakeholders
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods