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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Paper illustration for Solution Interview
Product Discovery
Solution Interview
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
Purposedifferent
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.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 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.When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.
Complexitydifferent
MediumHighMediumHigh
Timedifferent
2–4 h review as a planning range; preparation and evaluation additionalMehrere Wochen30-60 min je Interview4-5 Tage
Participantsdifferent
Designers, developers as users, and facilitation2-6 researchers plus sample5-10 Interviews5-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesSolution Feedback, Objection List, Validation NotesPrototype, Test Findings, Decision Rationale
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
OutcomesInnovationResearchQuantitative
ValidationInterviewsPrototype
Design sprintPrototypeValidationInnovation
Add more methods