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 CommentsARID (Active Reviews for Intermediate Designs)Architecture Decision Record
| Criterion |  Product Discovery Outcome-Driven Innovation |  Architecture Request for Comments |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | Mehrere Wochen | 1-3 Wochen vom Draft bis zur Entscheidung | 2–4 h review as a planning range; preparation and evaluation additional | 15-45 min |
Participantsdifferent | 2-6 researchers plus sample | 3-20 Reviewer | Designers, developers as users, and facilitation | 1-3 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | ADR File, Decision Log, Rationale |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureDecisionAsyncGovernance | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureRationaleDocumentationGovernance |