methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
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.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 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.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
HighMediumMediumLow
Timedifferent
Mehrere Wochen2–4 h review as a planning range; preparation and evaluation additional1-3 Wochen vom Draft bis zur Entscheidung15-45 min
Participantsdifferent
2-6 researchers plus sampleDesigners, developers as users, and facilitation3-20 Reviewer1-3
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncAsync
Outputdifferent
Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsADR File, Decision Log, Rationale
Tagsno overlap
OutcomesInnovationResearchQuantitative
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureDecisionAsyncGovernance
ArchitectureRationaleDocumentationGovernance
Add more methods