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 CommentsRAID LogATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Product Discovery Outcome-Driven Innovation |  Architecture Request for Comments |  Delivery RAID Log |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. |
Complexitydifferent | High | Medium | Low | High |
Timedifferent | Mehrere Wochen | 1-3 Wochen vom Draft bis zur Entscheidung | 30 min Setup, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-6 researchers plus sample | 3-20 Reviewer | 1-3 maintaining, briefing for everyone | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Async | Async | 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 | RAID Log, Status Report Source | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureDecisionAsyncGovernance | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskTradeoffsStakeholders |