View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Innovation Double Diamond | ![]() 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. | For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement. | 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 |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | Wochen bis Monate | Mehrere Wochen |
Participantsdifferent | Designers, developers as users, and facilitation | 3-12 | 2-6 researchers plus sample |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Problem Statement, Solution Options, Prototypes, Deliverables per Phase | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ProcessDivergenceInnovation | OutcomesInnovationResearchQuantitative |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






