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 Architecture Decision Record |  Facilitation Responsibility Poker |  Architecture Request for Comments |  Decision Making RAPID |
|---|---|---|---|---|
Purposedifferent | 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. | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 15-45 min | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min |
Participantsdifferent | 1-3 | 3-10 | 3-20 Reviewer | 3-12 |
Formatdifferent | Async | Workshop | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Responsibility Map, Role Agreements, Open Questions | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAPID Role Map, Recommendation, Decision Log |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RolesResponsibilityTeamFacilitation | ArchitectureDecisionAsyncGovernance | DecisionRolesGovernance |