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.

Selected:Assumption MappingARID (Active Reviews for Intermediate Designs)SurveysRiskiest Assumption Test
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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Surveys method illustration showing its working structure
UX Research
Surveys
Paper illustration of Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption Test
Purposedifferent
When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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 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.When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report.
Complexitysame
MediumMediumMediumMedium
Timedifferent
45-60 min2–4 h review as a planning range; preparation and evaluation additional3-14 Tage1-2 Wochen pro Iteration
Participantsdifferent
2-8Designers, developers as users, and facilitation50+2-6
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Assumption map, Test backlog, Risk rankingPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsSurvey Results, Charts, Segment InsightsPrioritized Assumption List, Test Plan, Results Report
Tags1 shared
AssumptionsRiskExperimentsValidation
ArchitectureEngineeringFeedbackValidationTasks
QuantitativeResearchValidation
ExperimentsValidationDiscoveryAssumptions
Add more methods