View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)RAID LogAssumption SurfacingRequest for Comments
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Delivery RAID Log |  Decision Making Assumption Surfacing |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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. | 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. | 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 | Medium | Low | Low | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30 min Setup, dann laufend | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | Designers, developers as users, and facilitation | 1-3 maintaining, briefing for everyone | 2-8 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | RAID Log, Status Report Source | Assumption List, Critical Assumptions, Learning Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | RiskTrackingStakeholdersGovernance | AssumptionsRiskDecisionDiscovery | ArchitectureDecisionAsyncGovernance |