View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Outcome-Driven InnovationRequest for CommentsDesign SprintARID (Active Reviews for Intermediate Designs)
| Criterion |  Product Discovery Outcome-Driven Innovation |  Architecture Request for Comments |  Innovation Design Sprint |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | 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. |
Complexitydifferent | High | Medium | High | Medium |
Timedifferent | Mehrere Wochen | 1-3 Wochen vom Draft bis zur Entscheidung | 4-5 Tage | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 2-6 researchers plus sample | 3-20 Reviewer | 5-8 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Prototype, Test Findings, Decision Rationale | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureDecisionAsyncGovernance | Design sprintPrototypeValidationInnovation | ArchitectureEngineeringFeedbackValidationTasks |