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) |  Product Discovery Outcome-Driven Innovation |  Innovation Lean Startup |
|---|---|---|---|
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. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | Mehrere Wochen | Wochen bis Monate je Lernzyklus |
Participantsdifferent | Designers, developers as users, and facilitation | 2-6 researchers plus sample | 2-8 |
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 | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | OutcomesInnovationResearchQuantitative | LeanStartupValidationMVP |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
