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
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 for Solution Interview
Product Discovery
Solution Interview
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 solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation.
Complexitydifferent
HighMediumHighMedium
Timedifferent
Mehrere Wochen2–4 h review as a planning range; preparation and evaluation additional1 Tag bis mehrere Wochen30-60 min je Interview
Participantsdifferent
2-6 researchers plus sampleDesigners, developers as users, and facilitation4-105-10 Interviews
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
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 LearningsSolution Feedback, Objection List, Validation Notes
Tagsno overlap
OutcomesInnovationResearchQuantitative
ArchitectureEngineeringFeedbackValidationTasks
InnovationPrototypeResearch
ValidationInterviewsPrototype
Add more methods