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 InnovationRAPIDATAM (Architecture Tradeoff Analysis Method)Request for Comments
| Criterion |  Product Discovery Outcome-Driven Innovation |  Decision Making RAPID |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Request for Comments |
|---|---|---|---|---|
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. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. |
Complexitydifferent | High | Medium | High | Medium |
Timedifferent | Mehrere Wochen | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-6 researchers plus sample | 3-12 | Evaluation team, architects, and relevant stakeholders | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | RAPID Role Map, Recommendation, Decision Log | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | OutcomesInnovationResearchQuantitative | DecisionRolesGovernance | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureDecisionAsyncGovernance |