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:SurveysARID (Active Reviews for Intermediate Designs)Design ThinkingOutcome-Driven Innovation
Criterion
Surveys method illustration showing its working structure
UX Research
Surveys
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
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Purposedifferent
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.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.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.
Complexitydifferent
MediumMediumHighHigh
Timedifferent
3-14 Tage2–4 h review as a planning range; preparation and evaluation additional1 Tag bis mehrere WochenMehrere Wochen
Participantsdifferent
50+Designers, developers as users, and facilitation4-102-6 researchers plus sample
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Survey Results, Charts, Segment InsightsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsProblem Statement, Prototype, Test LearningsDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses
Tagsno overlap
QuantitativeResearchValidation
ArchitectureEngineeringFeedbackValidationTasks
InnovationPrototypeResearch
OutcomesInnovationResearchQuantitative
Add more methods