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 calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Surveys method illustration showing its working structure
UX Research
Surveys
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.When a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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
MediumMediumLowHigh
Timedifferent
45-60 min3-14 Tage1-2 Tage1-4 Wochen
Participantsdifferent
2-850+1-41-6
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
Assumption map, Test backlog, Risk rankingSurvey Results, Charts, Segment InsightsArchitecture Document, Context View, Runtime View, Deployment ViewExperiment results, Decision log, Learning summary
Tagsno overlap
AssumptionsRiskExperimentsValidation
QuantitativeResearchValidation
ArchitectureDocumentationCommunication
ExperimentsGrowthAnalyticsValidation
Add more methods