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 Eisenhower Matrix |  Decision Making RAPID |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 15-30 min | 45-90 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 3-20 Reviewer | 1-6 | 3-12 | Designers, developers as users, and facilitation |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Eisenhower Matrix, Action List, Delegation Notes | RAPID Role Map, Recommendation, Decision Log | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | PrioritizationFocusTasks | DecisionRolesGovernance | ArchitectureEngineeringFeedbackValidationTasks |