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 Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
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)
Surveys method illustration showing its working structure
UX Research
Surveys
Purposedifferent
Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs.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 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.
Complexitydifferent
HighHighMediumMedium
Timedifferent
Mehrere Wochen1-4 Wochen2–4 h review as a planning range; preparation and evaluation additional3-14 Tage
Participantsdifferent
2-6 researchers plus sample1-6Designers, developers as users, and facilitation50+
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesExperiment results, Decision log, Learning summaryPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsSurvey Results, Charts, Segment Insights
Tagsno overlap
OutcomesInnovationResearchQuantitative
ExperimentsGrowthAnalyticsValidation
ArchitectureEngineeringFeedbackValidationTasks
QuantitativeResearchValidation
Add more methods