View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Decision Making Trade-off Analysis |  Product Discovery Assumption Mapping |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | 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. | With limited resources, quality, speed, cost, and risk almost always compete with each other. Trade-off Analysis makes these tensions explicit and prevents decisions from producing hidden side effects. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-120 min | 45-60 min | 45-90 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | 2-8 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Trade-off Matrix, Criteria List, Decision Rationale, Accepted Downsides | Assumption map, Test backlog, Risk ranking | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | TradeoffsDecisionCriteriaOptions | AssumptionsRiskExperimentsValidation | AssumptionsRiskDecisionDiscovery |