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 |  Delivery RAID Log |  Architecture arc42 |  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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | Low | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30 min Setup, dann laufend | 1-2 Tage | 45-90 min |
Participantsdifferent | 3-20 Reviewer | 1-3 maintaining, briefing for everyone | 1-4 | 2-8 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication | AssumptionsRiskDecisionDiscovery |