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:Outcome-Driven InnovationARID (Active Reviews for Intermediate Designs)Design ThinkingSurveys
Criterion
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Design Thinking as a learning loop: an observation notebook, a focused problem statement, different idea sketches, a cardboard prototype and user-test notes. Feedback leads to new understanding.
Innovation
Design Thinking
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.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.For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.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
HighMediumHighMedium
Timedifferent
Mehrere Wochen2–4 h review as a planning range; preparation and evaluation additional1 Tag bis mehrere Wochen3-14 Tage
Participantsdifferent
2-6 researchers plus sampleDesigners, developers as users, and facilitation4-1050+
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsProblem Statement, Prototype, Test LearningsSurvey Results, Charts, Segment Insights
Tagsno overlap
OutcomesInnovationResearchQuantitative
ArchitectureEngineeringFeedbackValidationTasks
InnovationPrototypeResearch
QuantitativeResearchValidation
Add more methods