View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)Jobs to Be DoneDesign ThinkingOutcome-Driven Innovation
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Jobs to Be Done |  Innovation Design Thinking |  Product Discovery Outcome-Driven Innovation |
|---|---|---|---|---|
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. | When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | 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 | Medium | Medium | High | High |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 Wochen | 1 Tag bis mehrere Wochen | Mehrere Wochen |
Participantsdifferent | Designers, developers as users, and facilitation | 5-12 Interviews | 4-10 | 2-6 researchers plus sample |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Job Stories, Outcome Statements, Opportunity List | Problem Statement, Prototype, Test Learnings | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | CustomerOutcomesNeeds | InnovationPrototypeResearch | OutcomesInnovationResearchQuantitative |