View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Decision Making Decision Rights Mapping |  Architecture Request for Comments |
|---|---|---|---|
Purposedifferent | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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 | Low | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 90-180 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 4-12 | 3-20 Reviewer |
Formatdifferent | Async | Workshop | Async |
Outputdifferent | RAID Log, Status Report Source | Decision Rights Matrix, Agreement | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tags1 shared | RiskTrackingStakeholdersGovernance | DecisionGovernanceAlignmentResponsibility | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
