View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Delphi Method |  Architecture Request for Comments |  Product Discovery Assumption Mapping |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | 1-4 Wochen | 1-3 Wochen vom Draft bis zur Entscheidung | 45-60 min | 60-90 min |
Participantsdifferent | 6-30 Experten | 3-20 Reviewer | 2-8 | 4-12 |
Formatdifferent | Async | Async | Workshop + async | Workshop |
Outputdifferent | Expert Forecast, Consensus Range, Assumption Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Assumption map, Test backlog, Risk ranking | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ForecastingExpertsDecisionStrategy | ArchitectureDecisionAsyncGovernance | AssumptionsRiskExperimentsValidation | RiskArchitectureWorkshopValidation |